[JIRA] (JENKINS-38149) TAP Extended Test Results throws NullPointerException
Title: Message Title Olof Kindgren assigned an issue to Oleg Nenashev Jenkins / JENKINS-38149 TAP Extended Test Results throws NullPointerException Change By: Olof Kindgren Assignee: Bruno P. Kinoshita Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications
Title: Message Title Itai Sanders commented on JENKINS-33507 Re: Bitbucket Server webhooks and Bitbucket Cloud build status notifications does this mean we also have the build status notification fixed? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36539) OK button disabled if project type chosen first
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-36539 OK button disabled if project type chosen first Change By: Daniel Beck Labels: lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31487) Job status not updated in web UI during build
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-31487 Job status not updated in web UI during build Change By: Daniel Beck Labels: lts-candidate progress regression status Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10912) Browser/JS memory leak in dashboard
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-10912 Browser/JS memory leak in dashboard Change By: Daniel Beck Labels: lts-candidate memory-leak Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31487) Job status not updated in web UI during build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31487 Re: Job status not updated in web UI during build Code changed in jenkins User: Matthew Reiter Path: core/src/main/java/hudson/widgets/BuildHistoryWidget.java core/src/main/java/hudson/widgets/HistoryWidget.java core/src/main/resources/hudson/widgets/HistoryWidget/index.jelly http://jenkins-ci.org/commit/jenkins/0268b988d5c88cd29be12ed25e95d5bc448c2840 Log: [FIXED JENKINS-31487] (#2542) There were two issues preventing the build history from updating properly: 1) The next build number being fetched wasn't taking into account running builds, so any builds already running when the page is refreshed would be ignored. The fix was to use nextBuildNumberToFetch if it is available (which is the case if there are running builds) and to fall back to the next build otherwise. 2) The first transient build key (used to clear out builds from the history that are being updated) wasn't being set when the page first loads. This was fixed by making getHistoryPageFilter calculate the value so that it happens in all cases rather than just during the ajax call. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31487) Job status not updated in web UI during build
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31487 Job status not updated in web UI during build Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26056) Workflow build step for Ant
Title: Message Title Jesse Glick started work on JENKINS-26056 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26056) Workflow build step for Ant
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-26056 Workflow build step for Ant Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38307) ATH erroneously installs detached plugins, causing needless restarts
Title: Message Title recampbell commented on JENKINS-38307 Re: ATH erroneously installs detached plugins, causing needless restarts It turns out that much of the trouble making this work is caused by JENKINS-37545. Plugins with old parent poms will pull in the correct dependencies when installed via the update center, but those dependencies won't be installed when the plugin is uploaded. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32148) highlight test result lines on hover
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-32148 highlight test result lines on hover Change By: Oleg Nenashev Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10912) Browser/JS memory leak in dashboard
Title: Message Title SCM/JIRA link daemon commented on JENKINS-10912 Re: Browser/JS memory leak in dashboard Code changed in jenkins User: lpancescu Path: war/src/main/webapp/scripts/hudson-behavior.js http://jenkins-ci.org/commit/jenkins/096614a6d72c19633909248cb5b06a179b8b4040 Log: JENKINS-10912 Use setInterval in refreshPart (#2539) JENKINS-10912 Use setInterval in refreshPart The current implementation of refreshPart creates a new closure every 5 seconds, which, in combination with XMLHttpRequest objects, results in a significant memory leak in all major browsers. By using window.setInterval to schedule periodic refreshes, only one closure per id is created. Please see issue #10912 in the Jenkins tracker for further details. Stop periodical calls if we can't find the div Don't check if isRunAsTest changed after page load Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-23991) Step error_message is not quoted in the scenario view, but IS quoted in the message error view
Title: Message Title James Nord assigned an issue to James Nord Jenkins / JENKINS-23991 Step error_message is not quoted in the scenario view, but IS quoted in the message error view Change By: James Nord Assignee: James Nord Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30597) Context menu arrows return 404
Title: Message Title James Nord commented on JENKINS-30597 Re: Context menu arrows return 404 confirmed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31940) Ability to sort on "All Tags" or at least they come presorted.
Title: Message Title James Nord closed an issue as Cannot Reproduce Jenkins / JENKINS-31940 Ability to sort on "All Tags" or at least they come presorted. Change By: James Nord Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31940) Ability to sort on "All Tags" or at least they come presorted.
Title: Message Title James Nord updated an issue Jenkins / JENKINS-31940 Ability to sort on "All Tags" or at least they come presorted. Change By: James Nord Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31940) Ability to sort on "All Tags" or at least they come presorted.
Title: Message Title James Nord commented on JENKINS-31940 Re: Ability to sort on "All Tags" or at least they come presorted. works here - the column headers are clicable which sorts the columns. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32593) FileNotFoundException in Cucumber Test Result Plugin with '<' or '>' in scenario name
Title: Message Title James Nord commented on JENKINS-32593 Re: FileNotFoundException in Cucumber Test Result Plugin with '<' or '>' in scenario name the embedded naming needs to sanitize the name more. than it does. Guessing the > is the issue in this case. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38195) Jenkins available plugin list is emtpy
Title: Message Title ye shengfei assigned an issue to ye shengfei Jenkins / JENKINS-38195 Jenkins available plugin list is emtpy Change By: ye shengfei Assignee: ye shengfei Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32830) Reporting broken when using maven with cucumber
Title: Message Title James Nord commented on JENKINS-32830 Re: Reporting broken when using maven with cucumber Looks like you are recording the tests as junit and cucmber format. You should only use cucumber format as a workaround, Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38195) Jenkins available plugin list is emtpy
Title: Message Title ye shengfei commented on JENKINS-38195 Re: Jenkins available plugin list is emtpy I met this bug,too with Jenkins ver. 2.7.4 fresh install. And When I manually install the plugins, the other error appear. list as the follow. java.io.IOException: Downloaded file /var/jenkins_home/plugins/github-api.jpi.tmp does not match expected SHA-1, expected '9tz3d4smuxOrjvBqUA2KEFoI8Oo=', actual 'QDYj/0lsPb6pcrhUvjEQyPg3wvc=' at hudson.model.UpdateCenter.verifyChecksums(UpdateCenter.java:1799) at hudson.model.UpdateCenter.access$1100(UpdateCenter.java:147) at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1950) at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1194) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1669) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1864) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1640) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35471) pom.xml dependency on org.jenkins-ci.plugins:junit version that does not exist
Title: Message Title James Nord resolved as Fixed https://github.com/jenkinsci/cucumber-testresult-plugin/commit/a527d3eb0218d87922fa542dfa6f973ab91d8eae Jenkins / JENKINS-35471 pom.xml dependency on org.jenkins-ci.plugins:junit version that does not exist Change By: James Nord Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-38287) test history not working in pipeline
Title: Message Title James Nord resolved as Fixed fixed by https://github.com/jenkinsci/cucumber-testresult-plugin/commit/7bd71003b2409624227eed5c18e016eb785232ef Jenkins / JENKINS-38287 test history not working in pipeline Change By: James Nord Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-38288) cucumber trend graph does not show up in a pipeline job
Title: Message Title James Nord closed an issue as Fixed Jenkins / JENKINS-38288 cucumber trend graph does not show up in a pipeline job Change By: James Nord Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32353) Integrate Ownership plugin with Pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32353 Re: Integrate Ownership plugin with Pipeline Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/com/synopsys/arc/jenkins/plugins/ownership/security/authorizeproject/OwnershipAuthorizeProjectStrategy.java http://jenkins-ci.org/commit/ownership-plugin/d404e86a6d7b411ee4bdce31b648c89a12404056 Log: JENKINS-32353 - Update Authorize Project integration to a Pipeline-compatible version Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32353) Integrate Ownership plugin with Pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32353 Re: Integrate Ownership plugin with Pipeline Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/com/synopsys/arc/jenkins/plugins/ownership/security/authorizeproject/OwnershipAuthorizeProjectStrategy.java http://jenkins-ci.org/commit/ownership-plugin/61a66a4d9428f1a04984c8b9d05b0a54885b Log: Merge pull request #54 from oleg-nenashev/bug/JENKINS-32353-authorize-project-pipeline JENKINS-32353 - Update Authorize Project integration to a Pipeline-compatible version Compare: https://github.com/jenkinsci/ownership-plugin/compare/0c8e5e65a785...61a66a4d9421 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Jesse Glick updated JENKINS-33511
Jenkins / JENKINS-33511
env.WORKSPACE should be available within node{} in Pipeline
Change By:
Jesse Glick
Status:
In Progress Review
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm
Title: Message Title
Mark Waite edited a comment on JENKINS-38126
Re: Credentials dropdown empty on git scm
[~arnaudlamy] can you give more details of the steps you take to reproduce the problem with the docker image jenkins:2.7.4? I tried the following steps and was unable to see the issue:# Run docker image jenkins:2.7.4 {noformat}docker run --rm -i --dns 8.8.8.8 --publish 9090:8080 -t jenkins:2.7.4{noformat}, record the initial login password from the window,# Open web browser to http://localhost:9090/# Paste the initial login password into the web browser# Select the "Install recommended plugins" box, wait for plugins to install# Complete the "Create First Admin User" form with my login information# Click the "Start using Jenkins" button# Click the "Credentials" link on the left side of the screen# Click the "Jenkins" credentials scope to open the Jenkins credentials scope# Click the "Global credentials" link to open the global credentials folder# Click "Add Credentials" to add a credential# Enter my github username and personal access token and save that credential# Create a new freestyle job named "bin"# Use Git as the SCM with the URL https://github.com/MarkEWaite//bin and the credential I previously defined (selected from the pick list)# Run the job and confirm that the username / password credential works for that job as expected I did not apply any limiting conditions to the visibility of those credentials. Maybe you had some additional configuration steps that are relevant?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm
Title: Message Title
Mark Waite edited a comment on JENKINS-38126
Re: Credentials dropdown empty on git scm
[~arnaudlamy] can you give more details of the steps you take to reproduce the problem with the docker image jenkins:2.7.4? I tried the following steps and was unable to see the issue:# Run docker image jenkins:2.7.4 from dockerhub with the command {{docker run --rm -i --dns 8.8.8.8 --publish 9090:8080 -t jenkins:2.7.4}}, note record the initial login password presented in from the window where docker was started ,# Open web browser to http://localhost:9090/# Paste the initial login password into the web browser# Select the "Install recommended plugins" box, wait for plugins to install# Complete the "Create First Admin User" form with my login information# Click the "Start using Jenkins" button# Click the "Credentials" link on the left side of the screen# Click the "Jenkins" credentials scope to open the Jenkins credentials scope# Click the "Global credentials" link to open the global credentials folder# Click "Add Credentials" to add a credential# Enter my github username and personal access token and save that credential# Create a new freestyle job named "bin"# Use Git as the SCM with the URL https://github.com/MarkEWaite//bin and the credential I previously defined (selected from the pick list)# Run the job and confirm that the username / password credential works for that job as expected
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm
Title: Message Title
Mark Waite edited a comment on JENKINS-38126
Re: Credentials dropdown empty on git scm
[~arnaudlamy] can you give more details of the steps you take to reproduce the problem with the docker image jenkins:2.7.4? I tried the following steps and was unable to see the issue:# Run docker image jenkins:2.7.4{ { noformat} docker run --rm -i --dns 8.8.8.8 --publish 9090:8080 -t jenkins:2.7.4 {noformat } } , record the initial login password from the window,# Open web browser to http://localhost:9090/# Paste the initial login password into the web browser# Select the "Install recommended plugins" box, wait for plugins to install# Complete the "Create First Admin User" form with my login information# Click the "Start using Jenkins" button# Click the "Credentials" link on the left side of the screen# Click the "Jenkins" credentials scope to open the Jenkins credentials scope# Click the "Global credentials" link to open the global credentials folder# Click "Add Credentials" to add a credential# Enter my github username and personal access token and save that credential# Create a new freestyle job named "bin"# Use Git as the SCM with the URL https://github.com/MarkEWaite//bin and the credential I previously defined (selected from the pick list)# Run the job and confirm that the username / password credential works for that job as expected
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm
Title: Message Title Mark Waite commented on JENKINS-38126 Re: Credentials dropdown empty on git scm arnaud lamy can you give more details of the steps you take to reproduce the problem with the docker image jenkins:2.7.4? I tried the following steps and was unable to see the issue: Run docker image jenkins:2.7.4 from dockerhub with the command docker run --rm -i --dns 8.8.8.8 --publish 9090:8080 -t jenkins:2.7.4, note the initial login password presented in the window where docker was started, Open web browser to http://localhost:9090/ Paste the initial login password into the web browser Select the "Install recommended plugins" box, wait for plugins to install Complete the "Create First Admin User" form with my login information Click the "Start using Jenkins" button Click the "Credentials" link on the left side of the screen Click the "Jenkins" credentials scope to open the Jenkins credentials scope Click the "Global credentials" link to open the global credentials folder Click "Add Credentials" to add a credential Enter my github username and personal access token and save that credential Create a new freestyle job named "bin" Use Git as the SCM with the URL https://github.com/MarkEWaite//bin and the credential I previously defined (selected from the pick list) Run the job and confirm that the username / password credential works for that job as expected Add Comment
[JIRA] (JENKINS-34488) Failing 'assert' hangs the pipeline
Title: Message Title ikedam commented on JENKINS-34488 Re: Failing 'assert' hangs the pipeline Classes not to serialize are defined here: https://github.com/jenkinsci/remoting/blob/remoting-2.62/src/main/java/hudson/remoting/ClassFilter.java#L56 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34488) Failing 'assert' hangs the pipeline
Title: Message Title ikedam commented on JENKINS-34488 Re: Failing 'assert' hangs the pipeline Exception thrownd by assert false error PowerAssertionError (id=128) cause PowerAssertionError (id=128) detailMessage "assert false" (id=162) stackTrace StackTraceElement[0] (id=166) suppressedExceptions Collections$UnmodifiableRandomAccessList (id=168) Exception thrownd by assert false: 'oh, no!' error AssertionError (id=125) cause AssertionError (id=125) detailMessage "oh, no!. _expression_: assert false: 'oh, no!'" (id=163) stackTrace StackTraceElement[0] (id=167) suppressedExceptions Collections$UnmodifiableRandomAccessList (id=169) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title Jesse Glick started work on JENKINS-33511 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36568) workflow script node step cannot trigger build on specific node
Title: Message Title Jesse Glick resolved as Not A Defect The label on node selects which node is allocated during its block. Wrapping build inside node makes no sense at all; the node context is ignored, you are just wasting an executor slot. Using LabelParameterValue is the appropriate solution for the requested problem. Jenkins / JENKINS-36568 workflow script node step cannot trigger build on specific node Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are
[JIRA] (JENKINS-34488) Failing 'assert' hangs the pipeline
Title: Message Title ikedam commented on JENKINS-34488 Re: Failing 'assert' hangs the pipeline This looks happen in here: https://github.com/jenkinsci/workflow-cps-plugin/blob/workflow-cps-2.17/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThreadGroup.java#L335 An exception occurs here, and codes to complete builds (such as calling fireCompletionHandlers) are skipped. This results builds not finish. Fails to add ErrorAction as it fails to be serialize to disks (attached a full thread dump): Caused by: java.lang.UnsupportedOperationException: Refusing to marshal org.codehaus.groovy.runtime.powerassert.PowerAssertionError for security reasons threaddump_halt_by_assert.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34488) Failing 'assert' hangs the pipeline
Title: Message Title ikedam updated an issue Jenkins / JENKINS-34488 Failing 'assert' hangs the pipeline Change By: ikedam Attachment: threaddump_halt_by_assert.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Jesse Glick commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
env.WORKSPACE = pwd()
should work in any environment. It is not safe for use inside parallel branches, though, so it is better to use
node {
withEnv(["WORKSPACE=${pwd()}"]) {
// …
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Jesse Glick edited a comment on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
{code}env.WORKSPACE = pwd(){code}should work in any environment , master or agent . It is not safe for use inside {{parallel}} branches, though, so it is better to use{code}node { withEnv(["WORKSPACE=${pwd()}"]) {// … }}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27039) Option for input or stage step to cancel older executions
Title: Message Title Jesse Glick commented on JENKINS-27039 Re: Option for input or stage step to cancel older executions cancel older builds for a specific PR, if more pushed commits triggered a new build? But not cancel any builds for a different PR Automatic if you are using a multibranch project. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27039) Option for input or stage step to cancel older executions
Title: Message Title Jesse Glick updated JENKINS-27039 Jenkins / JENKINS-27039 Option for input or stage step to cancel older executions Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38309) Make ForkScanner return Parallel Branches in same order as others
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38309 Re: Make ForkScanner return Parallel Branches in same order as others Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/graphanalysis/ForkScanner.java src/test/java/org/jenkinsci/plugins/workflow/graphanalysis/FlowScannerTest.java src/test/java/org/jenkinsci/plugins/workflow/graphanalysis/ForkScannerTest.java http://jenkins-ci.org/commit/workflow-api-plugin/dcd2152870040fe8dd1ee4fa616542b6bb3329dc Log: Ensure that parallels in ForkScanner follow the same reverse-order iteration, per JENKINS-38309 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38309) Make ForkScanner return Parallel Branches in same order as others
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-38309 Make ForkScanner return Parallel Branches in same order as others Issue Type: Improvement Assignee: Sam Van Oort Components: workflow-api-plugin Created: 2016/Sep/17 11:53 PM Priority: Major Reporter: Sam Van Oort When using the ForkScanner to walk through a flow graph, most things are returned in logical reverse order (end --> start, right), but parallels are done in the opposite (first branch, then second). The API doesn't guarantee parallel ordering but it is helpful for consumers to have the same guarantee in place for parallels too, since it turns out to be practical. Add Comment
[JIRA] (JENKINS-38300) Pull requests within a Github org folder / Bitbucket team not displaying
Title: Message Title
Vivek Pandey commented on JENKINS-38300
Re: Pull requests within a Github org folder / Bitbucket team not displaying
Its a regression for nested multibranch project. pipeline 'jenkins' is nested inside 'Core' folder. UI seems to be sending wrong URL to fetch run details of branch, https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/jenkins/branches/PR-2549/runs/1/. Its missing 'core' folder in the path. Correct URL is: https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/core/pipelines/jenkins/branches/PR-2549/runs/1/. 'self' links are generated correctly, GET on https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/Core/jenkins/branches/?filter=pull-requests=0=26 gives:
{
"_class": "io.jenkins.blueocean.rest.impl.pipeline.BranchImpl",
"_links": {
"queue": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/Core/pipelines/jenkins/branches/PR-2549/queue/"
},
"self": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/Core/pipelines/jenkins/branches/PR-2549/"
},
"activities": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/Core/pipelines/jenkins/branches/PR-2549/activities/"
},
"runs": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/Core/pipelines/jenkins/branches/PR-2549/runs/"
},
"actions": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/Core/pipelines/jenkins/branches/PR-2549/actions/"
}
},
"actions":[...],
"displayName": "PR-2549",
"estimatedDurationInMillis": -1,
"fullName": "Core/jenkins/PR-2549",
"lastSuccessfulRun": null,
"latestRun": {
"_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineRunImpl",
"_links": {
"nodes": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/Core/pipelines/jenkins/branches/PR-2549/runs/1/nodes/"
},
"self": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/Core/pipelines/jenkins/branches/PR-2549/runs/1/"
},
"steps": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/Core/pipelines/jenkins/branches/PR-2549/runs/1/steps/"
},
"log": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/Core/pipelines/jenkins/branches/PR-2549/runs/1/log/"
},
"actions": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/Core/pipelines/jenkins/branches/PR-2549/runs/1/actions/"
}
},
"actions": [...],
"artifacts": [],
"changeSet": [],
"durationInMillis": 0,
"enQueueTime": "2016-09-17T22:06:33.504+",
"endTime": null,
"estimatedDurationInMillis": -1,
"id": "1",
"organization": "jenkins",
"pipeline": "PR-2549",
"result": "UNKNOWN",
"runSummary": "?",
"startTime": "2016-09-17T22:06:33.505+",
"state": "RUNNING",
"type": "WorkflowRun",
"commitId": "d128e9b4a654cb6c98ab3c67df9229167098"
},
"name": "PR-2549",
[JIRA] (JENKINS-38307) ATH erroneously installs detached plugins, causing needless restarts
Title: Message Title recampbell started work on JENKINS-38307 Change By: recampbell Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38307) ATH erroneously installs detached plugins, causing needless restarts
Title: Message Title recampbell assigned an issue to recampbell Jenkins / JENKINS-38307 ATH erroneously installs detached plugins, causing needless restarts Change By: recampbell Assignee: Oliver Gondža recampbell Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25804) Whitelisted signature presets for Java standard APIs and Jenkins core APIs
Title: Message Title ikedam resolved as Fixed Christian Höltje You're right. The mechanism to define whitelists are already available, and I'll create pull requests each time when I want to whitelist something. Jenkins / JENKINS-25804 Whitelisted signature presets for Java standard APIs and Jenkins core APIs Change By: ikedam Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from
[JIRA] (TEST-97) Quick1 866 725 7490 Quickbooks tech support phone number
Title: Message Title Jesse Glick moved an issue test / TEST-97 Quick1 866 725 7490 Quickbooks tech support phone number Change By: Jesse Glick Project: Jenkins test Key: JENKINS TEST - 35405 97 Workflow: JNJira + In-Review Component/s: foo Component/s: accelerated-build-now-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to
[JIRA] (JENKINS-35405) Quick1 866 725 7490 Quickbooks tech support phone number
Title: Message Title Jesse Glick closed an issue as Won't Do Jenkins / JENKINS-35405 Quick1 866 725 7490 Quickbooks tech support phone number Change By: Jesse Glick Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38308) Changing type of parameter isn't updating
Title: Message Title kenorb created an issue Jenkins / JENKINS-38308 Changing type of parameter isn't updating Issue Type: Bug Assignee: Joel Johnson Components: ez-templates-plugin Created: 2016/Sep/17 11:14 PM Environment: EZ Templates 1.2.0, Jenkins ver. 2.7.1 Priority: Minor Reporter: kenorb I've String Parameter in the template and replaced it with Choice Parameter with the same name, so only type has changed. Now all jobs doesn't recognize that chance, even after re-saving. The only workaround seems to be removing that parameter from the job, so it's recreated. Add Comment
[JIRA] (JENKINS-38307) ATH erroneously installs detached plugins, causing needless restarts
Title: Message Title recampbell updated an issue Jenkins / JENKINS-38307 ATH erroneously installs detached plugins, causing needless restarts Change By: recampbell The acceptance test harness must restart Jenkins after plugin installation due to the fact that outdated, [detached plugins are installed|https://github.com/jenkinsci/acceptance-test-harness/blob/c1512e4da9dc3b4dd701988dae103eaec405ec25/src/main/java/org/jenkinsci/test/acceptance/controller/LocalController.java#L182] by default. As per this [outdated commit|https://github.com/jenkinsci/acceptance-test-harness/commit/61e55fa7517efd2ee41b61312d6659c0ce31d0a2], it looks like the intent is just to fix failing tests which have never had to declare detached plugins in their WithPlugins. One impact of this is that almost every test case must restart Jenkins because it installs updated plugins over the existing detached ones, which prevents dynamic deployment from working. I think we actually must take the hard path here and fix up the WithPlugins to be accurate. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38306) Directory name for @LocalData
Title: Message Title ikedam started work on JENKINS-38306 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38306) Directory name for @LocalData
Title: Message Title ikedam commented on JENKINS-38306 Re: Directory name for @LocalData https://github.com/jenkinsci/jenkins-test-harness/pull/36 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38306) Directory name for @LocalData
Title: Message Title ikedam updated JENKINS-38306 Jenkins / JENKINS-38306 Directory name for @LocalData Change By: ikedam Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38307) ATH erroneously installs detached plugins, causing needless restarts
Title: Message Title recampbell created an issue Jenkins / JENKINS-38307 ATH erroneously installs detached plugins, causing needless restarts Issue Type: Bug Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2016/Sep/17 11:11 PM Priority: Major Reporter: recampbell The acceptance test harness must restart Jenkins after plugin installation due to the fact that outdated, detached plugins are installed by default. As per this outdated commit, it looks like the intent is just to fix failing tests which have never had to declare detached plugins in their WithPlugins. I think we actually must take the hard path here and fix up the WithPlugins to be accurate. Add Comment
[JIRA] (JENKINS-38306) Directory name for @LocalData
Title: Message Title
ikedam created an issue
Jenkins / JENKINS-38306
Directory name for @LocalData
Issue Type:
Improvement
Assignee:
ikedam
Components:
jenkins-test-harness
Created:
2016/Sep/17 10:54 PM
Environment:
jenkins-2.14
Priority:
Minor
Reporter:
ikedam
@LocalData decides the directory use in the following way:
# /package/class/methodname
/package/class
So the data is usable from only one test cases or all test cases (with @LocalData) in a test. However, it's often the case that one wants to use data from multiple test cases, but not all test cases. It's great if one can specify the directory name with @LocalData like
public class Test {
@Rule public JenkinsRule j = new JenkinsRule();
@Test
@LocalData("config1")
public void config1_test1() throws Exception {...}
@Test
@LocalData("config1")
public void config1_test2() throws Exception {...}
@Test
@LocalData("config2")
public void config2_test1() throws Exception {...}
}
[JIRA] (JENKINS-38305) Remove --tty from docker exec
Title: Message Title Rafael Kassner created an issue Jenkins / JENKINS-38305 Remove --tty from docker exec Issue Type: Bug Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 2016/Sep/17 9:46 PM Environment: Plugin version 1.6.5 Priority: Minor Reporter: Rafael Kassner Hi, As pointed out here, docker exec will return the wrong status code when --tty is provided, thus failing jobs in Jenkins even though they should have been successful. I've written a small PR for that, but I'm not sure if we can just disable the tty. Any comments? Add Comment
[JIRA] (JENKINS-38304) Support multiple methods with @TestExtension
Title: Message Title ikedam updated JENKINS-38304 Jenkins / JENKINS-38304 Support multiple methods with @TestExtension Change By: ikedam Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38304) Support multiple methods with @TestExtension
Title: Message Title ikedam started work on JENKINS-38304 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38304) Support multiple methods with @TestExtension
Title: Message Title ikedam commented on JENKINS-38304 Re: Support multiple methods with @TestExtension https://github.com/jenkinsci/jenkins-test-harness/pull/35 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38304) Support multiple methods with @TestExtension
Title: Message Title ikedam created an issue Jenkins / JENKINS-38304 Support multiple methods with @TestExtension Issue Type: Improvement Assignee: ikedam Components: jenkins-test-harness Created: 2016/Sep/17 9:32 PM Environment: jenkins-test-harness-2.14 Priority: Minor Reporter: ikedam @TestExtension is applicable in following two ways: Applied to all test cases in that test. Applied to a specific test case. It's often the case that some class for tests is used by multiple test cases, but not by all cases in the test. It's is great if I can specify multiple test cases to @TestExtension. Add Comment
[JIRA] (JENKINS-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications
Title: Message Title Antonio Muñiz commented on JENKINS-33507 Re: Bitbucket Server webhooks and Bitbucket Cloud build status notifications Webhooks support for BB Server merged into master (not released yet). For the records: the plugin required at BB Server side is https://marketplace.atlassian.com/plugins/nl.topicus.bitbucket.bitbucket-webhooks/server/overview Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications
Title: Message Title Antonio Muñiz closed an issue as Fixed Jenkins / JENKINS-33507 Bitbucket Server webhooks and Bitbucket Cloud build status notifications Change By: Antonio Muñiz Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38303) pipeline script fails
Title: Message Title or gaizer created an issue Jenkins / JENKINS-38303 pipeline script fails Issue Type: Bug Assignee: vjuranek Components: groovy-plugin, pipeline Created: 2016/Sep/17 9:16 PM Environment: jenkins 2.7.4, just installed with all suggested plugins plus all pipeline plugins and groovy plugins (to check if it is the cause) Labels: pipeline jenkins groovy Priority: Blocker Reporter: or gaizer Hey, when i run a pipeline script (doesnt matter what script do I write), it fails. OS: ubuntu16.04 Jenkins version: 2.7.4 error: groovy.lang.GroovyRuntimeException: Failed to create Script instance for class: class WorkflowScript. Reason: java.lang.RuntimeException: java.lang.ClassNotFoundException: java.io.Serializable at org.codehaus.groovy.runtime.InvokerHelper.createScript(InvokerHelper.java:464) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:410) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:373) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:213) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.lang.RuntimeException:
[JIRA] (JENKINS-38302) BlueOcean compatibility
Title: Message Title Antonio Muñiz closed an issue as Fixed Jenkins / JENKINS-38302 BlueOcean compatibility Change By: Antonio Muñiz Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38302) BlueOcean compatibility
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-38302 BlueOcean compatibility Issue Type: Task Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Sep/17 8:47 PM Priority: Major Reporter: Antonio Muñiz Make the necessary changes to make BB multibranch project compatible with BlueOcean. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm
Title: Message Title arnaud lamy commented on JENKINS-38126 Re: Credentials dropdown empty on git scm @Gunter For info I can reproduce it with docker image: jenkins:2.7.4 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Israel Sotomayor commented on JENKINS-31155 Re: Workflow shared library improvements Same problem here when loading the library from Jenkinsfile I can see: Loading library github.com/moltin/jenkins-pipeline-library@master Creating git repository in /var/jenkins_home/caches/git-10e1b910805192749e5be85c3935e6d6 > git init /var/jenkins_home/caches/git-10e1b910805192749e5be85c3935e6d6 # timeout=10 Setting origin to https://github.com/moltin/jenkins-pipeline-library.git But when trying to use the Global Configuration the following it's thrown: Loading library github.com/moltin/jenkins-pipeline-library@branches/master java.lang.NullPointerException at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:74) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:150) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.add(LibraryAdder.java:131) So something different it's happening when loading the library from the Jenkinsfile vs Global configuration Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38283) jabber-plugin does not list out pipeline jobs
Title: Message Title kutzi commented on JENKINS-38283 Re: jabber-plugin does not list out pipeline jobs I haven't had the time to familiarise myself with the pipeline plugin and it may take some time for me to work on this - given my priorities have somewhat shifted away from Jenkins. So if you really want something to happen here: a Pull Request would be welcome! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37735) Aligning the check box in login page
Title: Message Title Ricardo Espirito Santo updated an issue Jenkins / JENKINS-37735 Aligning the check box in login page Change By: Ricardo Espirito Santo Labels: webpage Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37735) Aligning the check box in login page
Title: Message Title Ricardo Espirito Santo assigned an issue to Ricardo Espirito Santo Jenkins / JENKINS-37735 Aligning the check box in login page Change By: Ricardo Espirito Santo Assignee: Ricardo Espirito Santo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37735) Aligning the check box in login page
Title: Message Title Ricardo Espirito Santo updated an issue Jenkins / JENKINS-37735 Aligning the check box in login page Change By: Ricardo Espirito Santo Labels: web Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37735) Aligning the check box in login page
Title: Message Title Ricardo Espirito Santo updated an issue Jenkins / JENKINS-37735 Aligning the check box in login page Change By: Ricardo Espirito Santo Labels: web Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31801) Using Throttle Concurrent Builds in a Pipeline
Title: Message Title mcrooney commented on JENKINS-31801 Re: Using Throttle Concurrent Builds in a Pipeline Thanks Andrew, that'd be awesome! For now I am using the executor hack I described above, but it isn't very elegant so it'd be awesome to have native support for this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37789) Pipeline Config: No obvious way to specify "run on any node"
Title: Message Title Patrick Wolf closed an issue as Duplicate Jenkins / JENKINS-37789 Pipeline Config: No obvious way to specify "run on any node" Change By: Patrick Wolf Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38301) Add configuration for admin monitors
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-38301 Add configuration for admin monitors Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38301) Add configuration for admin monitors
Title: Message Title Daniel Beck updated JENKINS-38301 Jenkins / JENKINS-38301 Add configuration for admin monitors Change By: Daniel Beck Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38301) Add configuration for admin monitors
Title: Message Title Daniel Beck started work on JENKINS-38301 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-37962 REGRESSION: parallel karaoke not allowing branch selection or completing correctly Change By: Daniel Beck Labels: regression Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37774) Adding attachments causes duplicate attachments to be added
Title: Message Title Randall Hobbs commented on JENKINS-37774 Re: Adding attachments causes duplicate attachments to be added I actually resolved this problem - it turned out to be another plugin (I don't remember the plugin name right now). It was the reason for the duplicates. It's working as expected now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37774) Adding attachments causes duplicate attachments to be added
Title: Message Title Randall Hobbs resolved as Not A Defect Jenkins / JENKINS-37774 Adding attachments causes duplicate attachments to be added Change By: Randall Hobbs Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38301) Add configuration for admin monitors
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-38301 Add configuration for admin monitors Issue Type: New Feature Assignee: Unassigned Components: core Created: 2016/Sep/17 5:32 PM Priority: Minor Reporter: Daniel Beck I want to be able to configure which admin monitors are enabled/disabled. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38168) job-params being overwritten by template
Title: Message Title Marc Carter closed an issue as Fixed Jenkins / JENKINS-38168 job-params being overwritten by template Change By: Marc Carter Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38168) job-params being overwritten by template
Title: Message Title Marc Carter commented on JENKINS-38168 Re: job-params being overwritten by template Fixed in 1.2.3 Taras Sologub If you have saved the templates (and hence the children) under version 1.2.2 then your job-specific params have been overwritten. I hope you have a backup policy (ThinBackup plugin has served us well for years). Although this was a straight bug, templates always have the capacity to magnify a bad decision so should never be used without a backup plugin. I'll add this to the main README. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38168) job-params being overwritten by template
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38168 Re: job-params being overwritten by template Code changed in jenkins User: Marc Carter Path: src/main/java/com/joelj/jenkins/eztemplates/exclusion/JobParametersExclusion.java http://jenkins-ci.org/commit/ez-templates-plugin/f8d19ed2af0495a124be8d18251849c4d6a9baee Log: bugfix: JENKINS-38168 job-params being overwritten by template Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38300) Pull requests within a Github org folder / Bitbucket team not displaying
Title: Message Title Keith Zantow created an issue Jenkins / JENKINS-38300 Pull requests within a Github org folder / Bitbucket team not displaying Issue Type: Bug Assignee: Keith Zantow Components: blueocean-plugin Created: 2016/Sep/17 4:25 PM Priority: Major Reporter: Keith Zantow Issue not including the org / team folder name in the PR URL resulting in a 404 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37300) Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
Title: Message Title Lars Hupel commented on JENKINS-37300 Re: Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder By the way, I deployed an updated version from Git (based on ae30e9b), and the error disappears. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Jesse Glick commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace I will try to solve this for branch projects as part of JENKINS-34564, since these are especially likely to be created and discarded rapidly. I think a general implementation need not really be that difficult. Each node (master, agent) should just pay attention to when a workspace is used. (If in core, via WorkspaceList; otherwise, perhaps via WorkspaceListener.) Then record a workspaces.xml, a sibling of workspace/, with a list of records: relative workspace path, Item.fullName, timestamp. Periodically, or when an agent comes online, etc., iterate the list and check for jobs which no longer exist under that name (covers JENKINS-22240), or workspaces which have not been used in a long time. If in a plugin (JENKINS-26471) you could get fancy and modify behavior according to free disk space, etc. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26471) Split WorkspaceCleanupThread from core
Title: Message Title Jesse Glick commented on JENKINS-26471 Re: Split WorkspaceCleanupThread from core JENKINS-35907 might be useful for implementation. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37300) Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
Title: Message Title Lars Hupel commented on JENKINS-37300 Re: Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder hagzag A new release would be much appreciated. It's affecting us too. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38299) Allow modification to GitSCM from Pipeline
Title: Message Title Mark Waite assigned an issue to Jesse Glick Jenkins / JENKINS-38299 Allow modification to GitSCM from Pipeline Change By: Mark Waite Assignee: Mark Waite Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38299) Allow modification to GitSCM from Pipeline
Title: Message Title June Rhodes created an issue Jenkins / JENKINS-38299 Allow modification to GitSCM from Pipeline Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Sep/17 12:36 PM Priority: Minor Reporter: June Rhodes The GitHub organisation plugin automatically passes in an "scm" variable to Pipeline scripts, which allows you to use it like so: ``` checkout scm: scm ``` I want to be able to modify the `scm` variable, because there's no other way of checking out the merged result for PRs. In particular, I want to be able to do: ``` scm.getExtensions().add([$class: 'RelativeTargetDirectory', relativeTargetDir: name]) scm.getExtensions().add([$class: 'CleanCheckout']) ``` However, by default calling getExtensions is not allowed in Pipeline scripts (in the Groovy sandbox), which means I can't put this in my Pipeline shared library without getting everyone that uses it to whitelist those methods. Add Comment
[JIRA] (JENKINS-38298) Send Performance plugin metrics to InfluxDB
Title: Message Title Anthony Communier created an issue Jenkins / JENKINS-38298 Send Performance plugin metrics to InfluxDB Issue Type: Improvement Assignee: Aleksi Simell Components: influxdb-plugin Created: 2016/Sep/17 11:39 AM Priority: Minor Reporter: Anthony Communier It would be nice to be able to push Performance plugin metrics to InfluxDB Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38168) job-params being overwritten by template
Title: Message Title Marc Carter commented on JENKINS-38168 Re: job-params being overwritten by template Sigh, this is why I wasn't 100% keen on publishing this to jenkins central. Once code has been stabilised again, I'll stop any changes until we have a respectable set of tests to guard against whatever snafu happened here. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38168) job-params being overwritten by template
Title: Message Title Marc Carter assigned an issue to Marc Carter Jenkins / JENKINS-38168 job-params being overwritten by template Change By: Marc Carter Assignee: Joel Johnson Marc Carter Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27396) Elastic timeout
Title: Message Title ikedam updated JENKINS-27396 Jenkins / JENKINS-27396 Elastic timeout Change By: ikedam Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27396) Elastic timeout
Title: Message Title ikedam started work on JENKINS-27396 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27396) Elastic timeout
Title: Message Title ikedam commented on JENKINS-27396 Re: Elastic timeout https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/19 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36876) It should be possible to assemble-dependencies as jpi files
Title: Message Title Vincent Latombe resolved as Fixed Released in 1.119 Jenkins / JENKINS-36876 It should be possible to assemble-dependencies as jpi files Change By: Vincent Latombe Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37541) NPE while getting getSensitiveBuildVariables in a build
Title: Message Title Vincent Latombe updated JENKINS-37541 Released in 1.9 Jenkins / JENKINS-37541 NPE while getting getSensitiveBuildVariables in a build Change By: Vincent Latombe Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
