• Type: Bug
• Resolution: Duplicate
• Priority: Major
• Component/s: maven-plugin
• Labels:

  • javascript
  • maven
  • maven3
• Environment:

  Noticed this on 2.36 and also the latest stable version - 2.19
  Running on Redhat 6, Oracle JDK 1.7.95 64 bit
  
  Browsers used:
  Chrome 55.0.2883.87 m
  Internet Explorer 11.0.9600.18499

1. 

   POST.PNG

   72 kB

   2016-12-13 11:43

2. 

   POST_existing.PNG

   33 kB

   2016-12-13 11:51

3. config.xml

   3 kB

   2016-12-13 11:40

[JENKINS-40410] Maven goals not being saved

Croydon Dias created issue - 2016-12-13 11:38

Croydon Dias made changes - 2016-12-13 11:40

Attachment

New: config.xml [ 35154 ]

Croydon Dias made changes - 2016-12-13 11:40

Description

Original: Create a new job of type 'Maven project'. Enter a job name, any source url ( I used subversion), and set a maven goal in the 'Build' step. e.g. 'clean package'. Click save. Open the configure page of the job and you'll see that you're maven goals aren't saved at all. Try modifying it and saving again. I opened the network tools within Chrome, and noticed that the POST data sent to the jenkins server via the browser doesn't send the updated goals. Something wrong with the javascript I presume? ---- I upgraded our instance from jenkins 1.x to 2.x and noticed that we're unable to modify any of the maven goals for our jobs. I'm in the process of changing all our jobs to use a Jenkinsfile, but it would be nice if this core functionality would work in the meantime.

New: Create a new job of type 'Maven project'. Enter a job name, any source url ( I used subversion), and set a maven goal in the 'Build' step. e.g. 'clean package'. Click save. Open the configure page of the job and you'll see that you're maven goals aren't saved at all. Try modifying it and saving again. I opened the network tools within Chrome, and noticed that the POST data sent to the jenkins server via the browser doesn't send the updated goals. Something wrong with the javascript I presume? ---- I upgraded our instance from jenkins 1.x to 2.x and noticed that we're unable to modify any of the maven goals for our jobs. I'm in the process of changing all our jobs to use a Jenkinsfile, but it would be nice if this core functionality would work in the meantime. ---- I attached a config.xml for a simple job that shows this issue.

Croydon Dias made changes - 2016-12-13 11:43

Attachment

New: POST.PNG [ 35155 ]

Croydon Dias made changes - 2016-12-13 11:44

Description

Original: Create a new job of type 'Maven project'. Enter a job name, any source url ( I used subversion), and set a maven goal in the 'Build' step. e.g. 'clean package'. Click save. Open the configure page of the job and you'll see that you're maven goals aren't saved at all. Try modifying it and saving again. I opened the network tools within Chrome, and noticed that the POST data sent to the jenkins server via the browser doesn't send the updated goals. Something wrong with the javascript I presume? ---- I upgraded our instance from jenkins 1.x to 2.x and noticed that we're unable to modify any of the maven goals for our jobs. I'm in the process of changing all our jobs to use a Jenkinsfile, but it would be nice if this core functionality would work in the meantime. ---- I attached a config.xml for a simple job that shows this issue.

New: Create a new job of type 'Maven project'. Enter a job name, any source url ( I used subversion), and set a maven goal in the 'Build' step. e.g. 'clean package'. Click save. Open the configure page of the job and you'll see that you're maven goals aren't saved at all. Try modifying it and saving again. I opened the network tools within Chrome, and noticed that the POST data is sent to the jenkins server via the browser. (see attached pic) ---- I upgraded our instance from jenkins 1.x to 2.x and noticed that we're unable to modify any of the maven goals for our jobs. I'm in the process of changing all our jobs to use a Jenkinsfile, but it would be nice if this core functionality would work in the meantime. ---- I attached a config.xml for a simple job that shows this issue.

Croydon Dias made changes - 2016-12-13 11:46

Environment

Original: Noticed this on 2.36 and also the latest stable version - 2.19 Running on Redhat 6, Oracle JDK 1.7.95 64 bit

New: Noticed this on 2.36 and also the latest stable version - 2.19 Running on Redhat 6, Oracle JDK 1.7.95 64 bit Browsers used: Chrome 55.0.2883.87 m Internet Explorer 11.0.9600.18499

Croydon Dias made changes - 2016-12-13 11:50

Description

Original: Create a new job of type 'Maven project'. Enter a job name, any source url ( I used subversion), and set a maven goal in the 'Build' step. e.g. 'clean package'. Click save. Open the configure page of the job and you'll see that you're maven goals aren't saved at all. Try modifying it and saving again. I opened the network tools within Chrome, and noticed that the POST data is sent to the jenkins server via the browser. (see attached pic) ---- I upgraded our instance from jenkins 1.x to 2.x and noticed that we're unable to modify any of the maven goals for our jobs. I'm in the process of changing all our jobs to use a Jenkinsfile, but it would be nice if this core functionality would work in the meantime. ---- I attached a config.xml for a simple job that shows this issue.

New: Create a new job of type 'Maven project'. Enter a job name, any source url ( I used subversion), and set a maven goal in the 'Build' step. e.g. 'clean package'. Click save. Open the configure page of the job and you'll see that you're maven goals aren't saved at all. Try modifying it and saving again. I opened the network tools within Chrome, and noticed that: 1) For a newly created job the POST data is sent to the jenkins server via the browser. (see attached pic) !POST.PNG|thumbnail! 2) For an existing job that was migrated from jenkins 1.x to 2.x, the POST data sent from the jenkins server does not contain the new parameters. ---- I upgraded our instance from jenkins 1.x to 2.x and noticed that we're unable to modify any of the maven goals for our jobs. I'm in the process of changing all our jobs to use a Jenkinsfile, but it would be nice if this core functionality would work in the meantime. ---- I attached a config.xml for a simple job that shows this issue.

Croydon Dias made changes - 2016-12-13 11:51

Description

Original: Create a new job of type 'Maven project'. Enter a job name, any source url ( I used subversion), and set a maven goal in the 'Build' step. e.g. 'clean package'. Click save. Open the configure page of the job and you'll see that you're maven goals aren't saved at all. Try modifying it and saving again. I opened the network tools within Chrome, and noticed that: 1) For a newly created job the POST data is sent to the jenkins server via the browser. (see attached pic) !POST.PNG|thumbnail! 2) For an existing job that was migrated from jenkins 1.x to 2.x, the POST data sent from the jenkins server does not contain the new parameters. ---- I upgraded our instance from jenkins 1.x to 2.x and noticed that we're unable to modify any of the maven goals for our jobs. I'm in the process of changing all our jobs to use a Jenkinsfile, but it would be nice if this core functionality would work in the meantime. ---- I attached a config.xml for a simple job that shows this issue.

New: Create a new job of type 'Maven project'. Enter a job name, any source url ( I used subversion), and set a maven goal in the 'Build' step. e.g. 'clean package'. Click save. Open the configure page of the job and you'll see that you're maven goals aren't saved at all. Try modifying it and saving again. I opened the network tools within Chrome, and noticed that: 1) For a newly created job the POST data is sent to the jenkins server via the browser. (see attached pic) !POST.PNG|thumbnail! 2) For an existing job that was migrated from jenkins 1.x to 2.x, the POST data sent from the jenkins server does not contain the new parameters. ---- I upgraded our instance from jenkins 1.x to 2.x and noticed that we're unable to modify any of the maven goals for our jobs. I'm in the process of changing all our jobs to use a Jenkinsfile, but it would be nice if this core functionality would work in the meantime. ---- I attached a config.xml for a simple job that shows this issue.

Croydon Dias made changes - 2016-12-13 11:51

Attachment

New: POST_existing.PNG [ 35156 ]

Croydon Dias made changes - 2016-12-13 11:51

Description

Original: Create a new job of type 'Maven project'. Enter a job name, any source url ( I used subversion), and set a maven goal in the 'Build' step. e.g. 'clean package'. Click save. Open the configure page of the job and you'll see that you're maven goals aren't saved at all. Try modifying it and saving again. I opened the network tools within Chrome, and noticed that: 1) For a newly created job the POST data is sent to the jenkins server via the browser. (see attached pic) !POST.PNG|thumbnail! 2) For an existing job that was migrated from jenkins 1.x to 2.x, the POST data sent from the jenkins server does not contain the new parameters. ---- I upgraded our instance from jenkins 1.x to 2.x and noticed that we're unable to modify any of the maven goals for our jobs. I'm in the process of changing all our jobs to use a Jenkinsfile, but it would be nice if this core functionality would work in the meantime. ---- I attached a config.xml for a simple job that shows this issue.

New: Create a new job of type 'Maven project'. Enter a job name, any source url ( I used subversion), and set a maven goal in the 'Build' step. e.g. 'clean package'. Click save. Open the configure page of the job and you'll see that you're maven goals aren't saved at all. Try modifying it and saving again. I opened the network tools within Chrome, and noticed that: 1) For a newly created job the POST data is sent to the jenkins server via the browser. (see attached pic) !POST.PNG|thumbnail! 2) For an existing job that was migrated from jenkins 1.x to 2.x, the POST data sent from the jenkins server does not contain the new parameters. !POST_existing.PNG|thumbnail! ---- I upgraded our instance from jenkins 1.x to 2.x and noticed that we're unable to modify any of the maven goals for our jobs. I'm in the process of changing all our jobs to use a Jenkinsfile, but it would be nice if this core functionality would work in the meantime. ---- I attached a config.xml for a simple job that shows this issue.

Load more newer events