[JIRA] (JENKINS-33168) Junit plugin took 7 hours to complete recording test failures
Title: Message Title Tomasz Śniatowski commented on JENKINS-33168 Re: Junit plugin took 7 hours to complete recording test failures FWIW we worked around the issue by limiting the amount of history kept for the affected jobs (which is unfortunate as it limits the usefulness of the entire setup) 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-41646) Get token to use in groovy
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-41646
Re: Get token to use in groovy
Something like that should work{code:java}import com.cloudbees.jenkins.plugins.amazonecr.*import com.cloudbees.plugins.credentials.* import com.amazonaws.regions.Regions def credential = AmazonECSRegistryCredential(CredentialsScope.GLOBAL,'CREDENTIAL_ID',Regions.US_EAST_1,'Description',jenkins.model.Jenkins.getInstance()) hudson.util.Secret token = credential.getPassword(){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-41646) Get token to use in groovy
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-41646
Re: Get token to use in groovy
Something like that should work{code:java}import com.cloudbees.jenkins.plugins.amazonecr.* import com.cloudbees.plugins.credentials.* def credential = AmazonECSRegistryCredential(CredentialsScope.GLOBAL,'CREDENTIAL_ID',Regions.US_EAST_1,'Description',jenkins.model.Jenkins.getInstance()) hudson.util.Secret token = credential.getPassword(){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-41646) Get token to use in groovy
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-41646 Re: Get token to use in groovy Something like that should work import com.cloudbees.jenkins.plugins.amazonecr.* def credential = AmazonECSRegistryCredential(CredentialsScope.GLOBAL,'CREDENTIAL_ID',Regions.US_EAST_1,'Description',jenkins.model.Jenkins.getInstance()) hudson.util.Secret token = credential.getPassword() 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-34666) JUnit test durations accounted improperly
Title: Message Title Sean Flanigan edited a comment on JENKINS-34666 Re: JUnit test durations accounted improperly I've just edited [~haw777]'s description by putting some text in bold (for clarity, I hope).I'm running JUnit plugin 1.19, with .xml files (1 per test class) generated by maven-failsafe-plugin:2.19.1/junit-4.12, and I'm seeing identical problems, except that the top-level Test Results page doesn't show any durations. Perhaps because I'm using a Maven job instead of Freestyle. 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-34666) JUnit test durations accounted improperly
Title: Message Title Sean Flanigan edited a comment on JENKINS-34666 Re: JUnit test durations accounted improperly I've just edited [~haw777]'s description by putting some text in bold (for clarity, I hope).I'm running JUnit plugin 1.19, with .xml files generated by maven- surefire failsafe -plugin:2.19.1/junit-4.12, and I'm seeing identical problems, except that the top-level Test Results page doesn't show any durations. Perhaps because I'm using a Maven job instead of Freestyle. 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-34666) JUnit test durations accounted improperly
Title: Message Title Sean Flanigan edited a comment on JENKINS-34666 Re: JUnit test durations accounted improperly I've just edited [~haw777]'s description by putting some text in bold (for clarity, I hope).I'm running JUnit plugin 1.19, with .xml files generated by Surefire maven-surefire-plugin:2.19.1 / JUnit junit-4.12 , and I'm seeing identical problems, except that the top-level Test Results page doesn't show any durations. Perhaps because I'm using a Maven job instead of Freestyle. 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-34666) JUnit test durations accounted improperly
Title: Message Title Sean Flanigan commented on JENKINS-34666 Re: JUnit test durations accounted improperly I've just edited Christopher Head's description by putting some text in bold (for clarity, I hope). I'm running JUnit plugin 1.19, with .xml files generated by Surefire/JUnit, and I'm seeing identical problems, except that the top-level Test Results page doesn't show any durations. Perhaps because I'm using a Maven job instead of Freestyle. 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-34666) JUnit test durations accounted improperly
Title: Message Title Sean Flanigan updated an issue Jenkins / JENKINS-34666 JUnit test durations accounted improperly Change By: Sean Flanigan The details page for a single test shows the duration for that specific test.The * details page for a single class * shows a table with a list of tests, along with the duration for each test. However, the duration * at the top * of the class detail page (“Took N seconds”) is not the sum of the durations of tests in that class, but erroneously also * includes the durations of tests in all other classes * as well (even classes in other packages).The * details page for a package * shows a table with a list of classes, with * every single class showing * the same duration ( * the duration of the entire job * , the same as the class details page). However, the total package duration at the top of the detail page (“Took N seconds”) is the sum of the durations of tests only within that package, and is therefore in general less than the duration shown for a single class within the package.Finally, the top-level Test Results page shows the proper total duration and the proper duration for each package (matching the package duration shown on the package details page).This is with a jUnit XML file generated by py.test. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40799) Swarm plugin changelog has not been updated for 3 releases
Title: Message Title Oleg Nenashev commented on JENKINS-40799 Re: Swarm plugin changelog has not been updated for 3 releases I've taken the issue just to deliver the fixes. I'll also try to contact the maintainer in order to get the proper release 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-40799) Swarm plugin changelog has not been updated for 3 releases
Title: Message Title Oleg Nenashev started work on JENKINS-40799 Change By: Oleg Nenashev 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-40799) Swarm plugin changelog has not been updated for 3 releases
Title: Message Title Oleg Nenashev commented on JENKINS-40799 Re: Swarm plugin changelog has not been updated for 3 releases The remoting needs to be updated to 3.4.1 or above 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-40799) Swarm plugin changelog has not been updated for 3 releases
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-40799 Swarm plugin changelog has not been updated for 3 releases Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi 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-41627) Naginator plugin uses user credentials of failed run
Title: Message Title Aleksi Grönlund updated an issue Jenkins / JENKINS-41627 Naginator plugin uses user credentials of failed run Change By: Aleksi Grönlund When pressing Re-try after failed build, Naginator plugin is using user credentials of that previous failed build. Those could be credentials of Username can belong to another user. With this This feature makes it is possible to overtake bypass the user security authorization rules. This is causing security problems. Would it be possible to change Could this feature plug- in Naginator feature to change ? It would be better to use current user (who is pressing Re-try button) credentials in Re-try feature by default (for example having global config checkbox settings 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 emai
[JIRA] (JENKINS-34666) JUnit test durations accounted improperly
Title: Message Title Sean Flanigan updated an issue Jenkins / JENKINS-34666 JUnit test durations accounted improperly Change By: Sean Flanigan Issue Type: Improvement Bug 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-41627) Naginator plugin uses user credentials of failed run
Title: Message Title Aleksi Grönlund updated an issue Jenkins / JENKINS-41627 Naginator plugin uses user credentials of failed run Change By: Aleksi Grönlund We are using Jenkins to deploy applications. Application deployment logic is defined in template item (template-project-plugin used). This login also contains security authorization rules based on username. Different users having deployment rights to different environments. When pressing Re-try after failed build, Naginator plugin is using user credentials of that previous failed build. Those could be credentials of another user. With this feature it is possible to overtake user security authorization rules. This is causing security problems. Would it be possible to change this feature in Naginator? It would be better to use current user (who is pressing Re-try button) credentials in Re-try by default (for example having global config checkbox settings for this). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You rece
[JIRA] (JENKINS-41650) More documentation on setting up rocketchatnotifier
Title: Message Title Sean Flanigan created an issue Jenkins / JENKINS-41650 More documentation on setting up rocketchatnotifier Issue Type: New Feature Assignee: Martin Reinhardt Components: rocket-chat-notifier-plugin Created: 2017/Feb/02 6:43 AM Priority: Minor Reporter: Sean Flanigan There's not much documentation yet, but it seems like the setup requires someone's username and password to be stored in Jenkins. Can this plugin work with the Incoming WebHook Integration feature in Rocket.Chat? (I'm dealing with 0.46.0.) Or some sort of API key? Add Comment
[JIRA] (JENKINS-39521) Full Log does not render newlines
Title: Message Title Michael Neale edited a comment on JENKINS-39521 Re: Full Log does not render newlines if it is shown as HTML - will it behave correctly or will console annotators mess with it? If so - best to show plain text and probably show the classic console view for those that want to use annotators for now? EDIT: oh that plain wrapped like [~strml] suggested could be good to - worth a try. 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-39521) Full Log does not render newlines - or use correct content type (weird HTML like artifacts)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39521 Full Log does not render newlines - or use correct content type (weird HTML like artifacts) Change By: Michael Neale Summary: Full Log does not render newlines - or use correct content type (weird HTML like artifacts) 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-39521) Full Log does not render newlines
Title: Message Title Michael Neale commented on JENKINS-39521 Re: Full Log does not render newlines if it is shown as HTML - will it behave correctly or will console annotators mess with it? If so - best to show plain text and probably show the classic console view for those that want to use annotators for 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-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title
Denis Boulas updated an issue
Jenkins / JENKINS-33510
dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Change By:
Denis Boulas
Priority:
Minor Critical
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-41649) Make Open Blue Ocean open to /blue/
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41649 Make Open Blue Ocean open to /blue/ Issue Type: Story Assignee: Tom FENNELLY Components: blueocean-plugin Created: 2017/Feb/02 6:13 AM Priority: Minor Reporter: Michael Neale Stapler does a 302 on /blue to /blue/ - which can be quite high (no idea why its redirects are so bad, but they are, and coupled with latency means an extra 300ms!). If possible, makes sense to just go to the right place ideally. Add Comment This
[JIRA] (JENKINS-39811) Upgrading slack plugin breaks jenkins
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-39811 Re: Upgrading slack plugin breaks jenkins Some workaround are explained in this thread: https://github.com/jenkinsci/slack-plugin/issues/188#issuecomment-246655313 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-41587) Multijob : Phase job blocks if MultiJob parent comes in the queue
Title: Message Title Gaurav Joshi updated an issue Jenkins / JENKINS-41587 Multijob : Phase job blocks if MultiJob parent comes in the queue Change By: Gaurav Joshi Labels: multi-job 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-41648) Jenkins hangs during build; webpage unresponsive
Title: Message Title Giovanni Porta closed an issue as Fixed Jenkins / JENKINS-41648 Jenkins hangs during build; webpage unresponsive Change By: Giovanni Porta Status: Resolved Closed 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-41648) Jenkins hangs during build; webpage unresponsive
Title: Message Title Giovanni Porta resolved as Fixed Permissions problem. Jenkins / JENKINS-41648 Jenkins hangs during build; webpage unresponsive Change By: Giovanni Porta 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 options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41547) Container must have a max-width
Title: Message Title Josh McDonald started work on JENKINS-41547 Change By: Josh McDonald 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-41648) Jenkins hangs during build; webpage unresponsive
Title: Message Title Giovanni Porta created an issue Jenkins / JENKINS-41648 Jenkins hangs during build; webpage unresponsive Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Feb/02 5:10 AM Environment: OS: Ubuntu 16.04.1 x64 - deployed on DigitalOcean Jenkins: 2.32.2 Java: openjdk-8 (8u121) All the recommend plugins are installed, plus GitHub. Priority: Blocker Reporter: Giovanni Porta My project is very small and building it only involves running a shell script with one argument, in which it just calls a jar file that initiates the build. For some reason, building goes fine and I'm able to watch things work on the console output, then all of a sudden the console output stops and the Jenkins page is unresponsive. I have to restart Jenkins to get the webpage back, and the build ends up not even being there. When I go to the build's output directory, I can see it never finished since a core .json file is missing. Jenkins doesn't crash if the build itself has an error near the beginning and doesn't proceed. It seems to only happen when the build is going on for a long period of time, and it occurs at the process where the script is downloading the libraries. For the record, this is my first time using Jenkins. service jenkins status returns the following: jenkins.service - LSB: Start Jenkins at boot time Loaded: loaded (/etc/init.d/jenkins; bad; vendor preset: enabled) Active: active (exited) since Thu 2017-02-02 04:47:18 UTC; 10min ago Docs: man:systemd-sysv-generator(8) Process: 7262 ExecStop=/etc/init.d/jenkins stop (code=exited, status=0/SUCCESS)
[JIRA] (JENKINS-41554) Navigation disappears if the page content is longer than the window height
Title: Message Title Josh McDonald stopped work on JENKINS-41554 Change By: Josh McDonald Status: In Progress Open 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-41554) Navigation disappears if the page content is longer than the window height
Title: Message Title Josh McDonald resolved as Fixed Fixed in JDL 0.0.108 Jenkins / JENKINS-41554 Navigation disappears if the page content is longer than the window height Change By: Josh McDonald 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 options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41554) Navigation disappears if the page content is longer than the window height
Title: Message Title Josh McDonald commented on JENKINS-41554 Re: Navigation disappears if the page content is longer than the window height JDL Fix is in https://github.com/jenkinsci/jenkins-design-language/pull/140 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-41647) Review all dependencies and upgrade to latest versions
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41647 Review all dependencies and upgrade to latest versions Issue Type: Task Assignee: Vivek Pandey Components: blueocean-plugin Created: 2017/Feb/02 3:17 AM Priority: Major Reporter: James Dumay I just performed an upgrade of an older Jenkins home to beta 21. Pipeline visualization didn't render correctly unless I upgraded to the latest Pipeline plugins. We should analyse all our dependencies and upgrade to the latest versions as a minimum, as this is what we test with on blueocean.io Add Comment
[JIRA] (JENKINS-40174) Missing authentication during git checkout and git-lfs
Title: Message Title Mark Waite edited a comment on JENKINS-40174 Re: Missing authentication during git checkout and git-lfs A pre-release of large file support is being tested now. You can download the [git client plugin|https://github.com/MarkEWaite/docker/blob/50c2c1c67232462cb1f7a5e75bd73d3611e6be9b/ref/plugins/git-client.jpi] and the [git plugin|https://github.com/MarkEWaite/docker/blob/ 50c2c1c67232462cb1f7a5e75bd73d3611e6be9b c9d4beeec4c861bdcbfe692f8060ee78c98da4b3 /ref/plugins/git.jpi] from the lts-with-plugins branch of my docker instance.I deeply appreciate comments on the [pull request|https://github.com/jenkinsci/git-plugin/pull/463] which say "I've installed the pre-release of this plugin and am using it successfully". I also deeply appreciate comments which indicate when a problem has been encountered. 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-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Mark Waite edited a comment on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use A pre-release of large file support is being tested now. You can download the [git client plugin|https://github.com/MarkEWaite/docker/blob/50c2c1c67232462cb1f7a5e75bd73d3611e6be9b/ref/plugins/git-client.jpi] and the [git plugin|https://github.com/MarkEWaite/docker/blob/ 50c2c1c67232462cb1f7a5e75bd73d3611e6be9b c9d4beeec4c861bdcbfe692f8060ee78c98da4b3 /ref/plugins/git.jpi] from the lts-with-plugins branch of my docker instance.I deeply appreciate comments on the [pull request|https://github.com/jenkinsci/git-plugin/pull/463] which say "I've installed the pre-release of this plugin and am using it successfully". I also deeply appreciate comments which indicate when a problem has been encountered. 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-38708) git checkout is run without credentials
Title: Message Title Mark Waite edited a comment on JENKINS-38708 Re: git checkout is run without credentials A pre-release of large file support is being tested now. You can download the [git client plugin|https://github.com/MarkEWaite/docker/blob/50c2c1c67232462cb1f7a5e75bd73d3611e6be9b/ref/plugins/git-client.jpi] and the [git plugin|https://github.com/MarkEWaite/docker/blob/ 50c2c1c67232462cb1f7a5e75bd73d3611e6be9b c9d4beeec4c861bdcbfe692f8060ee78c98da4b3 /ref/plugins/git.jpi] from the lts-with-plugins branch of my docker instance.I deeply appreciate comments on the [pull request|https://github.com/jenkinsci/git-plugin/pull/463] which say "I've installed the pre-release of this plugin and am using it successfully". I also deeply appreciate comments which indicate when a problem has been encountered. 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-35687) Add explicit support for git lfs
Title: Message Title Mark Waite edited a comment on JENKINS-35687 Re: Add explicit support for git lfs A pre-release of large file support is being tested now. You can download the [git client plugin|https://github.com/MarkEWaite/docker/blob/50c2c1c67232462cb1f7a5e75bd73d3611e6be9b/ref/plugins/git-client.jpi] and the [git plugin|https://github.com/MarkEWaite/docker/blob/ 50c2c1c67232462cb1f7a5e75bd73d3611e6be9b c9d4beeec4c861bdcbfe692f8060ee78c98da4b3 /ref/plugins/git.jpi] from the lts-with-plugins branch of my docker instance.I deeply appreciate comments on the [pull request|https://github.com/jenkinsci/git-plugin/pull/463] which say "I've installed the pre-release of this plugin and am using it successfully". I also deeply appreciate comments which indicate when a problem has been encountered. 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-41646) Get token to use in groovy
Title: Message Title Denis Boulas created an issue Jenkins / JENKINS-41646 Get token to use in groovy Issue Type: New Feature Assignee: Ivan Fernandez Calvo Components: amazon-ecr-plugin Created: 2017/Feb/02 2:31 AM Priority: Minor Reporter: Denis Boulas Hello there! Is it possible to get ECR token to use in groovy code? What is the proper way to do that? For e.g. I want to implement some logic to check if tag is already present in the repo with curl for e.g. Thanks! Add Comment This message wa
[JIRA] (JENKINS-41645) Better error messages when illegal identifiers are used in an `environment` block
Title: Message Title
Christopher Orr commented on JENKINS-41645
Re: Better error messages when illegal identifiers are used in an `environment` block
Another one is quoted names:
environment {
// Failure [what-about-single-quotes] is a constant _expression_, but it should be a variable
'what-about-single-quotes' = 'unlikely'
}
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-40417) COPY command with multiple source file fails
Title: Message Title Matt Dodge commented on JENKINS-40417 Re: COPY command with multiple source file fails This was happening to me too but updating the plugin solved it for me. I was on 1.35 but now on 1.38 the issue doesn't seem to occur. 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-41602) Global Shared Library git ref overrides the project repo git info
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-41602 Global Shared Library git ref overrides the project repo git info Change By: Mark Waite Component/s: git-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 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-41645) Better error messages when illegal identifiers are used in an `environment` block
Title: Message Title
Christopher Orr created an issue
Jenkins / JENKINS-41645
Better error messages when illegal identifiers are used in an `environment` block
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Feb/02 1:01 AM
Environment:
Plugin 1.0
Priority:
Minor
Reporter:
Christopher Orr
Presumably environment variable names must be legal Groovy identifiers (although generally, I don't think environment variables have as a strict a naming convention). When trying to use various illegal identifiers, I got various different error messages:
pipeline {
agent any
stages {
stage('Foo') {
environment {
// Failure: Expected name=value pairs
3D_GLASSES = 'no'
// Failure: Expected name=value pairs
123ABC = 'bad'
// Failure: expecting token in range: '0'..'9', found 'X'
456_XYZ = 'numeric literal?'
// Failure: ((what - about) - hyphens) is a binary _expression_
what-about-hyphens = 'binary _expression_?'
// OK
LEGAL_GROOVY_IDENTIFIER = 'yay'
}
steps {
sh 'env'
}
}
}
}
I would expect some linting when editing the Pipeline (well, the editor does catch the 456_XYZ case), and nicer error messages at runtime.
[JIRA] (JENKINS-35687) Add explicit support for git lfs
Title: Message Title Mark Waite commented on JENKINS-35687 Re: Add explicit support for git lfs A pre-release of large file support is being tested now. You can download the git client plugin and the git plugin from the lts-with-plugins branch of my docker instance. I deeply appreciate comments on the pull request which say "I've installed the pre-release of this plugin and am using it successfully". I also deeply appreciate comments which indicate when a problem has been encountered. 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-40174) Missing authentication during git checkout and git-lfs
Title: Message Title Mark Waite commented on JENKINS-40174 Re: Missing authentication during git checkout and git-lfs A pre-release of large file support is being tested now. You can download the git client plugin and the git plugin from the lts-with-plugins branch of my docker instance. I deeply appreciate comments on the pull request which say "I've installed the pre-release of this plugin and am using it successfully". I also deeply appreciate comments which indicate when a problem has been encountered. 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-38708) git checkout is run without credentials
Title: Message Title Mark Waite commented on JENKINS-38708 Re: git checkout is run without credentials A pre-release of large file support is being tested now. You can download the git client plugin and the git plugin from the lts-with-plugins branch of my docker instance. I deeply appreciate comments on the pull request which say "I've installed the pre-release of this plugin and am using it successfully". I also deeply appreciate comments which indicate when a problem has been encountered. 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-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Mark Waite commented on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use A pre-release of large file support is being tested now. You can download the git client plugin and the git plugin from the lts-with-plugins branch of my docker instance. I deeply appreciate comments on the pull request which say "I've installed the pre-release of this plugin and am using it successfully". I also deeply appreciate comments which indicate when a problem has been encountered. 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-33168) Junit plugin took 7 hours to complete recording test failures
Title: Message Title Sean Flanigan commented on JENKINS-33168 Re: Junit plugin took 7 hours to complete recording test failures Thanks for including those details Tomasz Śniatowski. Very helpful. I've been investigating a bit (in the code and the issue tracker), and it looks like the JUnit plugin's method CaseResult.getPreviousResult (which is called by the Test Stability plugin) gets really slow when there isn't enough heap memory to hold enough JUnit results in memory. TestResultAction uses WeakReferences to hold the actual results, so if there's not enough memory to go around, the system will spend a lot of time re-reading results from disk. It would get worse when tests are failing because JUnit retains stdout/stderr for each failing test, thus using more memory. An idle Jenkins would have less memory pressure, which would explain why it's harder to reproduce the problem. I'm not sure if there's an easy way of reducing the memory requirements, so for now throwing more heap memory at the problem might be the only workaround. A proper solution will probably require setting up some sort of indexed database to hold test results for efficient queries, updated after each test run. Although, it might help to iterate over the TestResult s differently, such that each build's TestResult s is examined exactly once. Right now, I think it may be loading previous builds' complete TestResult s many times, and also calling TestObject.findCorrespondingResult(id) many times. Refs: https://issues.jenkins-ci.org/browse/JENKINS-24457 and https://issues.jenkins-ci.org/browse/JENKINS-10175 (including comments) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41644) SCM providers could provide the format for their "commit id"
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41644 SCM providers could provide the format for their "commit id" Issue Type: Story Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/02 12:54 AM Priority: Minor Reporter: Michael Neale In git it is conventional to write a commit id as #abc1234 Other SCMs may have other conventions. Would be nice if the UI could reflect their preferences vs assuming everyone uses git. Add Comment This message was sent by A
[JIRA] (JENKINS-38540) Add REST API redirects for /runs and /queue
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38540 Add REST API redirects for /runs and /queue Change By: James Dumay Sprint: pacific, atlantic, indian, arctic, tasman , pannonian 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-41307) Alternate editor launch button
Title: Message Title Michael Neale resolved as Fixed Jenkins / JENKINS-41307 Alternate editor launch button Change By: Michael Neale 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-41554) Navigation disappears if the page content is longer than the window height
Title: Message Title Josh McDonald started work on JENKINS-41554 Change By: Josh McDonald 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-41547) Container must have a max-width
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41547 Container must have a max-width Change By: James Dumay Priority: Blocker Critical 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-41118) Allow custom workspaces in declarative pipeline
Title: Message Title
Jianfei Liao commented on JENKINS-41118
Re: Allow custom workspaces in declarative pipeline
Another use case we run into is that we have a bunch of Go projects that we rely on a specific layout (per the Golang development recommendation: https://golang.org/doc/code.html#Workspaces). We used to be able to control this with Scripted Pipeline with a top level `ws("some-path")` step. With the Declarative Pipeline, we had to basically wrap a `script {}` block on each step to achieve the same result.
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-41433) Add new API for "permissions"
Title: Message Title James Dumay commented on JENKINS-41433 Re: Add new API for "permissions" Vivek Pandey can this also cover the "I am an administrator" case for JENKINS-41096 ? 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-38751) Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38751 Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job Change By: James Dumay * Do not start this work if the new headers are not on master** Scope** Add the "exit to classic" link to both the header of application and to the run modal*Original request*If I navigate to a Pipeline, deep within a GitHub Organization Folder, it's impossible to quickly get to the "classic" UI with my current browsing context.If I want to get from a detail page for a pull request run, I need to open a new window, click the folder, click the repository, click pull requests, click the appropriate pull request job, then click the build number.It would be nicer if there was a little link in the header of the detail page which allowed me to "view in classic" or something like that. That way I could easily go from [this detail view|https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-2577/2] to [this classic page|https://ci.jenkins.io/job/Core/job/jenkins/view/Pull%20Requests/job/PR-2577/2/] without wanting to flip my desk. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40877 Display links to Github PR and Branch on Pipeline Result Change By: James Dumay * Do not start this work if the new headers are not on master** Scope** Modify the Run screen design so we can surface a branch or PR link* If the run is for a PR then it should read "Pull Request" instead of "Branch"*Notes*There is an API for retrieving the pull request and branch links [here|https://github.com/jenkinsci/blueocean-plugin/pull/686]*Design Brief*Developers desire a link back to Github for or branch and pull requests contextually in Blue Ocean.At a minimum it would be useful if a developer could click through to the web interface on Github for a branch or PR from the Run screen. 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 jenkinsc
[JIRA] (JENKINS-41068) Obsolate branch directories are not removed from job directory on master
Title: Message Title davidkarlsen commented on JENKINS-41068 Re: Obsolate branch directories are not removed from job directory on master Has any 2.0 official been released now which wasn't retracted from the plugin updates list due to some hard breaking changes? 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-38088) Allow re-run of all runs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38088 Re: Allow re-run of all runs Code changed in jenkins User: Ivan Meredith Path: src/test/js/notMultibranch/pipelineRunning.js http://jenkins-ci.org/commit/blueocean-acceptance-test/e51f13ed4cd0d842bf0d4da7dde00cdee4d4b4a9 Log: JENKINS-38088 Check for replay buttons 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-41401) We want to use user scoped credentials with SCMs
Title: Message Title James Dumay updated JENKINS-41401 Jenkins / JENKINS-41401 We want to use user scoped credentials with SCMs Change By: James Dumay 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-41588) Review the run details under non-multibranch conditions
Title: Message Title James Dumay closed an issue as Incomplete Jenkins / JENKINS-41588 Review the run details under non-multibranch conditions Change By: James Dumay Status: Open Closed Resolution: Incomplete 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-41293) Testing and upgrading of SCM changes
Title: Message Title James Dumay updated JENKINS-41293 Jenkins / JENKINS-41293 Testing and upgrading of SCM changes Change By: James Dumay 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-41401) We want to use user scoped credentials with SCMs
Title: Message Title James Dumay started work on JENKINS-41401 Change By: James Dumay 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-41588) Review the run details under non-multibranch conditions
Title: Message Title James Dumay assigned an issue to Brody Maclean Jenkins / JENKINS-41588 Review the run details under non-multibranch conditions Change By: James Dumay Assignee: Brody Maclean 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-41638) "Open Blue Ocean" button doesn't work unless the server URL is set correctly
Title: Message Title James Dumay edited a comment on JENKINS-41638 Re: "Open Blue Ocean" button doesn't work unless the server URL is set correctly Need to be more defensive here . for sure - this is a terrible source of friction! 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-41638) "Open Blue Ocean" button doesn't work unless the server URL is set correctly
Title: Message Title James Dumay commented on JENKINS-41638 Re: "Open Blue Ocean" button doesn't work unless the server URL is set correctly Need to be more defensive 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-41643) Developer should receive a notification if someone is editing the same Pipeline and branch
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41643 Developer should receive a notification if someone is editing the same Pipeline and branch Issue Type: Story Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/01 11:02 PM Priority: Minor Reporter: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you
[JIRA] (JENKINS-41352) New dashboard cards
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-41352
New dashboard cards
Change By:
James Dumay
The favourite card needs to be updated to reflect the new leaner design: * Thinner* Aligned elements* Has last run informationFollow on from: https://issues.jenkins-ci.org/browse/JENKINS-39341 (which is nearly ready) Please make sure that commit I'd is not prefixed with a {{#}}
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-41642) Handle when favouriting a pipeline fails
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41642 Handle when favouriting a pipeline fails Change By: James Dumay Summary: Handle when favouriting a pipeline fails 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-41642) Handle when favouriting fails
Title: Message Title
James Dumay created an issue
Jenkins / JENKINS-41642
Handle when favouriting fails
Issue Type:
Improvement
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2017/Feb/01 10:57 PM
Priority:
Minor
Reporter:
James Dumay
If favouriting fails for any reason we should show an error toast to the user to tell them the error has failed. Usually there is a reason sent for the failed rest call and this is safe to send to the user You can make favouriting fail by:
Create a multibranch pipeline with no branches
Go to the dashboard
Favourite the pipeline
REST call will fail with:
{
"message" : "no master branch to favorite",
"code" : 400,
"errors" : [ ]
}
[JIRA] (JENKINS-40814) Jenkins Github trigger doesnt work unless build start manually
Title: Message Title Jose Ordaz edited a comment on JENKINS-40814 Re: Jenkins Github trigger doesnt work unless build start manually I have the same issue . but it does not work after trigger manually In my case I am using Ubuntu 16.04.1 LTS on google cloud with Jenkins 2.32.1-0 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-41189) [Pipeline] Some non-CPS transformable code will not throw errors
Title: Message Title Sean Sutherland commented on JENKINS-41189 Re: [Pipeline] Some non-CPS transformable code will not throw errors What is the reason for this check not occurring in non-sandbox mode? If the CPS transformation isnt going to happen either way, I still need to know about it even if I'm not using the sandbox 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-40814) Jenkins Github trigger doesnt work unless build start manually
Title: Message Title Jose Ordaz commented on JENKINS-40814 Re: Jenkins Github trigger doesnt work unless build start manually I have the same issue. In my case I am using Ubuntu 16.04.1 LTS on google cloud with Jenkins 2.32.1-0 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-41641) Timeout waits even when slave is offline
Title: Message Title Shauvik Roy Choudhary created an issue Jenkins / JENKINS-41641 Timeout waits even when slave is offline Issue Type: Bug Assignee: Unassigned Components: pipeline, workflow-basic-steps-plugin Created: 2017/Feb/01 10:42 PM Environment: org.jenkins-ci.main:jenkins-war:2.32.1 org.springframework:spring-webmvc:2.5.6.SEC03 commons-beanutils:commons-beanutils:1.8.3 oro:oro:2.0.8 org.jenkins-ci:task-reactor:1.4 org.kohsuke.stapler:stapler-jrebel:1.248 org.jenkins-ci.ui:handlebars:1.1.1 org.jenkins-ci.dom4j:dom4j:1.6.1-jenkins-4 org.jenkins-ci.modules:instance-identity:2.1 org.ow2.asm:asm-analysis:4.0 stax:stax-api:1.0.1 org.jenkins-ci.main:jenkins-core:2.32.1 org.jenkins-ci.modules:ssh-cli-auth:1.2 org.jenkins-ci:bytecode-compatibility-transformer:1.8 commons-jelly:commons-jelly-tags-xml:1.1 org.ow2.asm:asm-commons:4.0 org.kohsuke:access-modifier-annotation:1.4 org.samba.jcifs:jcifs:1.3.17-kohsuke-1 org.springframework:spring-dao:1.2.9 org.springframework:spring-aop:2.5.6.SEC03 org.fusesource.jansi:jansi:1.11 commons-httpclient:commons-httpclient:3.1 com.github.jnr:jnr-posix:3.0.1 org.codehaus.woodstox:wstx-asl:3.2.9 org.springframework:spring-core:2.5.6.SEC03 org.kohsuke:asm5:5.0.1 com.google.inject:guice:4.0 org.mindrot:jbcrypt:0.3m org.apache.commons:commons-compress:1.10 com.github.jnr:jnr-constants:0.8.5 org.jvnet.libzfs:libzfs:0.5 org.jenkins-ci.ui:bootstrap:1.3.2 jfree:jcommon:1.0.12 org.jvnet:tiger-types:2.2 javax.xml.stream:stax-api:1.0-2 org.kohsuke:trilead-putty-extension:1.2 org.kohsuke.stapler:stapler-adjunct-zeroclipboard:1.3.5-1 org.apache.ant:ant:1.8.4 org.kohsuke.stapler:stapler-adjunct-codemirror:1.3 com.jcraft:jzlib:1.1.3-kohsuke-1 org.jenkins-ci.modules:slave-installer:1.5 org.kohsuke:libpam4j:1.8 org.jenkins-ci.main:remoting:3.2 commons-jelly:commons-jelly-tags-fmt:1.0 jline:jline:2.12 org.ow2.asm:asm-util:4.0 javax.servlet:jstl:1.1.0 org.jenkins-ci:winstone:3.1 com.github.jnr:jnr-ffi:1.0.7 net.java.sezpoz:sezpoz:1.12 org.apache.ant:ant-launcher:1.8.4 org.jenkins-ci:trilead-ssh2:build217-jenkins-8 commons-io:commons-io:2.4 com.github.jnr:jffi:1.2.7 org.jenkins-ci.modules:upstart-slave-installer:1.1 org.jvnet.hudson:jtidy:4aug2000r7-dev-hudson-1 org.jenkins-ci.modules:windows-slave-installer:1.6 org.kohsuke.stapler:stapler-jelly:1.248 org.springframework:spring-web:2.5.6.SEC03 org.jvnet.winp:winp:1.24 org.kohsuke.stapler:stapler-adjunct-timeline:1.4 org.apache.mina:mina-core:2.0.5 javax.annotation:javax.annotation-api:1.2 org.jenkins-ci:crypto-util:1.1 commons-discovery:commons-discovery:0.4 org.jenkins-ci.
[JIRA] (JENKINS-40899) Transitive plugin dependencies not correctly checked when using snapshots
Title: Message Title recampbell reopened an issue Not a duplicate, but clearly related. Jenkins / JENKINS-40899 Transitive plugin dependencies not correctly checked when using snapshots Change By: recampbell Resolution: Fixed Status: Closed Reopened 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
[JIRA] (JENKINS-38021) Accessing unset global variable cause master to hang
Title: Message Title Jesse Glick updated JENKINS-38021 Under some conditions I get a hang, corrected by the JENKINS-31484 fix. The build is interruptible however. Jenkins / JENKINS-38021 Accessing unset global variable cause master to hang Change By: Jesse Glick Status: In Review Resolved 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...@googl
[JIRA] (JENKINS-41501) Regression: Activity pagination is broken
Title: Message Title Ivan Meredith updated JENKINS-41501 Jenkins / JENKINS-41501 Regression: Activity pagination is broken Change By: Ivan Meredith 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-38617) SystemExit check when running system groovy scripts
Title: Message Title Victor Martinez resolved as Fixed Next release: 0.6.0 Jenkins / JENKINS-38617 SystemExit check when running system groovy scripts Change By: Victor Martinez 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-41638) "Open Blue Ocean" button doesn't work unless the server URL is set correctly
Title: Message Title Michael Neale commented on JENKINS-41638 Re: "Open Blue Ocean" button doesn't work unless the server URL is set correctly yes this comes up quite frequently. It seems people don't set it correctly, ignore warnings. Bits of Jenkins will never work correctly, but the main part does. I suspect it is peoples first attempt at setting it up... 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-38617) SystemExit check when running system groovy scripts
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38617 Re: SystemExit check when running system groovy scripts Code changed in jenkins User: Victor Martinez Path: pom.xml src/main/java/org/jenkins/ci/plugins/jenkinslint/JenkinsLintAction.java src/main/java/org/jenkins/ci/plugins/jenkinslint/check/GroovySystemExitChecker.java src/test/java/org/jenkins/ci/plugins/jenkinslint/check/GroovySystemExitCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/2f95712cd9f736442019ce1cc21644beeb3bca92 Log: Merge pull request #3 from jenkinsci/groovy_system_exit JENKINS-38617 System exit when running system groovy. Compare: https://github.com/jenkinsci/jenkinslint-plugin/compare/2d83215ddbf0...2f95712cd9f7 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-40899) Transitive plugin dependencies not correctly checked when using snapshots
Title: Message Title recampbell closed an issue as Fixed Alvaro, this looks like a clear duplicate, please reopen if not. Jenkins / JENKINS-40899 Transitive plugin dependencies not correctly checked when using snapshots Change By: recampbell 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, v
[JIRA] (JENKINS-41640) Scroll spy improvements
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41640 Scroll spy improvements Change By: Michael Neale Sprint: post-release 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-41640) Scroll spy improvements
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41640 Scroll spy improvements Change By: Michael Neale Post 2.0 need to revisit scrollspy in classic for some overdue fixes: https://github.com/jenkinsci/jenkins/pull/2339 Not really a blue ocean task per se, but putting here to plan for it as it is needed post 1.0 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-41640) Scroll spy improvements
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41640 Scroll spy improvements Issue Type: Story Assignee: Tom FENNELLY Components: blueocean-plugin Created: 2017/Feb/01 10:08 PM Priority: Minor Reporter: Michael Neale Post 2.0 need to revisit scrollspy in classic for some overdue fixes: https://github.com/jenkinsci/jenkins/pull/2339 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40461) ${DURATION} template contains "and counting" even at job conclusion, for pipeline builds
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-40461
Re: ${DURATION} template contains "and counting" even at job conclusion, for pipeline builds
Code changed in jenkins User: Peter Major Path: src/main/java/jenkins/plugins/hipchat/utils/BuildUtils.java src/test/java/jenkins/plugins/hipchat/utils/BuildUtilsTest.java http://jenkins-ci.org/commit/hipchat-plugin/2d37483dc858145ea2df35dc658d5345a065199b Log: JENKINS-40461 Fix duration template variable
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-40461) ${DURATION} template contains "and counting" even at job conclusion, for pipeline builds
Title: Message Title
aldaris resolved as Fixed
Thanks for the report, this should be fixed in the upcoming 2.1.0 version.
Jenkins / JENKINS-40461
${DURATION} template contains "and counting" even at job conclusion, for pipeline builds
Change By:
aldaris
Status:
Open Resolved
Assignee:
aldaris
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You rece
[JIRA] (JENKINS-31484) Endless loop in DefaultInvoker.getProperty when accessing field via getter/setter without @
Title: Message Title Jesse Glick updated JENKINS-31484 Jenkins / JENKINS-31484 Endless loop in DefaultInvoker.getProperty when accessing field via getter/setter without @ Change By: Jesse Glick Status: In Review 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-41639) Jenkins won't shut down
Title: Message Title Oleg Nenashev commented on JENKINS-41639 Re: Jenkins won't shut down Reassigned to Antonio Muñiz 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-41639) Jenkins won't shut down
Title: Message Title Oleg Nenashev assigned an issue to Antonio Muñiz Jenkins / JENKINS-41639 Jenkins won't shut down Change By: Oleg Nenashev Assignee: Oleg Nenashev Antonio Muñiz 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-41639) Jenkins won't shut down
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-41639 Jenkins won't shut down Change By: Oleg Nenashev Component/s: pipeline-milestone-step-plugin Component/s: _unsorted 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-41639) Jenkins won't shut down
Title: Message Title Aris Tsev created an issue Jenkins / JENKINS-41639 Jenkins won't shut down Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2017/Feb/01 9:54 PM Priority: Minor Reporter: Aris Tsev failed to send event to listener of class org.jenkinsci.plugins.pipeline.milestone.MilestoneStepExecution$CleanupJobsOnDelete java.lang.NullPointerException at org.jenkinsci.plugins.pipeline.milestone.MilestoneStepExecution$CleanupJobsOnDelete.onDeleted(MilestoneStepExecution.java:348) at hudson.model.listeners.ItemListener$4.apply(ItemListener.java:205) at hudson.model.listeners.ItemListener$4.apply(ItemListener.java:203) at hudson.model.listeners.ItemListener.forAll(ItemListener.java:167) at hudson.model.listeners.ItemListener.fireOnDeleted(ItemListener.java:203) at jenkins.model.Jenkins.onDeleted(Jenkins.java:2931) at jenkins.model.Jenkins.onDeleted(Jenkins.java:303) at hudson.model.AbstractItem.delete(AbstractItem.java:574) at hudson.model.Job.delete(Job.java:683) at hudson.model.AbstractItem.doDoDelete(AbstractItem.java:533) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:108) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.
[JIRA] (JENKINS-39521) Full Log does not render newlines
Title: Message Title James Dumay commented on JENKINS-39521 Re: Full Log does not render newlines James Nord thanks we've seen this too. We are going to look at it in the next sprint 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-38617) SystemExit check when running system groovy scripts
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38617 Re: SystemExit check when running system groovy scripts Code changed in jenkins User: Victor Martinez Path: pom.xml src/main/java/org/jenkins/ci/plugins/jenkinslint/check/GroovySystemExitChecker.java http://jenkins-ci.org/commit/jenkinslint-plugin/0a852b69d3269df95f84f82a35a4dcc2b331ae89 Log: JENKINS-38617 Refactored a bit to remove Optional plugin dependency by using Reflection 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-41189) [Pipeline] Some non-CPS transformable code will not throw errors
Title: Message Title Jesse Glick commented on JENKINS-41189 Re: [Pipeline] Some non-CPS transformable code will not throw errors Note that this check only happens in sandbox mode currently. 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-41189) [Pipeline] Some non-CPS transformable code will not throw errors
Title: Message Title Jesse Glick resolved as Cannot Reproduce In a fresh 2.7.19.1 instance: Started by user admin [Pipeline] End of Pipeline java.lang.UnsupportedOperationException: Calling public static java.util.List org.codehaus.groovy.runtime.DefaultGroovyMethods.findAll(java.util.List,groovy.lang.Closure) on a CPS-transformed closure is not yet supported (JENKINS-26481); encapsulate in a @NonCPS method, or use Java-style loops at org.jenkinsci.plugins.workflow.cps.GroovyClassLoaderWhitelist.checkJenkins26481(GroovyClassLoaderWhitelist.java:86) at org.jenkinsci.plugins.workflow.cps.GroovyClassLoaderWhitelist.permitsStaticMethod(GroovyClassLoaderWhitelist.java:56) at … at WorkflowScript.run(WorkflowScript:1) at … Finished: FAILURE Jenkins / JENKINS-41189 [Pipeline] Some non-CPS transformable code will not throw errors Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment
[JIRA] (JENKINS-37366) Pipeline "currentBuild" should expose project name
Title: Message Title Shauvik Roy Choudhary commented on JENKINS-37366 Re: Pipeline "currentBuild" should expose project name Can you use `env.JOB_NAME` instead? http://stackoverflow.com/a/41345704 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-41638) "Open Blue Ocean" button doesn't work unless the server URL is set correctly
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41638 "Open Blue Ocean" button doesn't work unless the server URL is set correctly Issue Type: Improvement Assignee: Tom FENNELLY Components: blueocean-plugin Created: 2017/Feb/01 9:46 PM Priority: Minor Reporter: James Dumay Ive fielded multiple support requests where the server URL was not the same as the URL Jenkins was accessed from. The "Open Blue Ocean" button seems not to work. Is there a way that we can make the button work based on the URL it was accessed from? Add Comment
[JIRA] (JENKINS-41501) Regression: Activity pagination is broken
Title: Message Title Ivan Meredith started work on JENKINS-41501 Change By: Ivan Meredith 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-40321) Job notification settings not respected in multibranch pipeline
Title: Message Title aldaris resolved as Not A Defect Both the global notifications and the now deprecated (and soon to be removed) HipChatJobProperty rely on the job having the HipChat post build action being present in the job configuration. Pipeline jobs do not have post build actions, hence the only viable way of sending notifications from those is to use the hipchatSend DSL as part of the pipeline definition. Jenkins / JENKINS-40321 Job notification settings not respected in multibranch pipeline Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38871) Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Undefined parameter var in token ENV], action = [Fail the build]
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38871 Re: Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Undefined parameter var in token ENV], action = "" the build] Code changed in jenkins User: Alex Earl Path: src/main/java/org/jenkinsci/plugins/tokenmacro/DataBoundTokenMacro.java http://jenkins-ci.org/commit/token-macro-plugin/65fabc0bb02fa64fc17fd5e1b12d39f3a9fa1eb5 Log: Fix JENKINS-38871 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-41636) Maven projects using Maven 3.0.x don't show annotations in console log since 2.44 / 2.32.2
Title: Message Title Jesse Glick updated JENKINS-41636 Jenkins / JENKINS-41636 Maven projects using Maven 3.0.x don't show annotations in console log since 2.44 / 2.32.2 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-40799) Swarm plugin changelog has not been updated for 3 releases
Title: Message Title Tamal Saha updated an issue Jenkins / JENKINS-40799 Swarm plugin changelog has not been updated for 3 releases Change By: Tamal Saha Priority: Minor Major 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.
