[JIRA] (JENKINS-37706) Document help message for include/exclude fields
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-37706 Document help message for include/exclude fields Issue Type: New Feature Assignee: Antonio Muñiz Attachments: bitbucket-branch-source-fields.png Components: bitbucket-branch-source-plugin Created: 2016/Aug/26 5:32 AM Environment: ButBucket Branch Source 1.6 Priority: Minor Reporter: Allan BURDAJEWICZ Need to add a help message for the Include and Exclude fields. It is not always clear what kind of pattern can be used. Add Comment
[JIRA] (JENKINS-35856) JDL component for Dialog
Title: Message Title Josh McDonald stopped work on JENKINS-35856 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-35826) Pagination for the pipeline list
Title: Message Title Keith Zantow updated JENKINS-35826 Jenkins / JENKINS-35826 Pagination for the pipeline list Change By: Keith Zantow Status: In Review Resolved Resolution: Done 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-35788) Pagination for Summary tabs
Title: Message Title Keith Zantow updated JENKINS-35788 Jenkins / JENKINS-35788 Pagination for Summary tabs Change By: Keith Zantow Status: In Review Closed Resolution: Done 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-37705) Double download in freestyle jobs
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37705 Double download in freestyle jobs Change By: Michael Neale Sprint: 1.0-beta-1 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-27618) Workflow support for NUnit plugin
Title: Message Title Bruno P. Kinoshita stopped work on JENKINS-27618 Change By: Bruno P. Kinoshita 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-27618) Workflow support for NUnit plugin
Title: Message Title Bruno P. Kinoshita resolved as Fixed Pull request merged. Version 0.18 released. Jenkins / JENKINS-27618 Workflow support for NUnit plugin Change By: Bruno P. Kinoshita 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-37705) Double download in freestyle jobs
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-37705 Double download in freestyle jobs Issue Type: Bug Assignee: Keith Zantow Attachments: Screen Shot 2016-08-26 at 1.47.57 PM.png Components: blueocean-plugin Created: 2016/Aug/26 4:21 AM Priority: Minor Reporter: Michael Neale See attached image. Pretty self explanatory. I mean, maybe double the icons makes it twice as good! Add Comment
[JIRA] (JENKINS-37544) Regression storybook support for dashboard is broken
Title: Message Title Keith Zantow updated JENKINS-37544 Jenkins / JENKINS-37544 Regression storybook support for dashboard is broken Change By: Keith Zantow 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-37544) Regression storybook support for dashboard is broken
Title: Message Title Keith Zantow updated an issue Jenkins / JENKINS-37544 Regression storybook support for dashboard is broken Change By: Keith Zantow Comment: BO storybook is using JDL code to run, and it's incompatible... no surprise there. 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-37544) Regression storybook support for dashboard is broken
Title: Message Title Keith Zantow commented on JENKINS-37544 Re: Regression storybook support for dashboard is broken BO storybook is using JDL code to run, and it's incompatible... no surprise there. 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-27618) Workflow support for NUnit plugin
Title: Message Title Bruno P. Kinoshita started work on JENKINS-27618 Change By: Bruno P. Kinoshita 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-37704) REGRESSION: Karaoke mode is busted on master
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37704 REGRESSION: Karaoke mode is busted on master Change By: Michael Neale You cannot stop karaoke by scrolling up or clicking on the log. It just keeps taking you to the bottom of the page.Additionally, clicking back on a completed run sometimes shows a step in non completed step (see attached). The project I used to reproduce this: https://github.com/kzantow/failure-project This was ok as of commit: https://github.com/jenkinsci/blueocean-plugin/commit/dc3e155cab3cc15cf472756c5c64ca5a214c731d I believe, so a recent change. I have not triaged it closer to that when it happened, it seems some time ago, so probably just worth forging ahead . 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-37544) Regression storybook support for dashboard is broken
Title: Message Title Keith Zantow started work on JENKINS-37544 Change By: Keith Zantow 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-37024) Opening the result modal should open over the existing content
Title: Message Title Keith Zantow started work on JENKINS-37024 Change By: Keith Zantow 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-37704) REGRESSION: Karaoke mode is busted on master
Title: Message Title James Dumay commented on JENKINS-37704 Re: REGRESSION: Karaoke mode is busted on master Michael Neale I reset my branch back to dc3e155cab3cc15cf472756c5c64ca5a214c731d and found it had the same problem 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-37704) REGRESSION: Karaoke mode is busted on master
Title: Message Title James Dumay commented on JENKINS-37704 Re: REGRESSION: Karaoke mode is busted on master Hmm did some testing and looks like this has been broken for some time... went back as far as last weeks release and it was stuffed there 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-37704) REGRESSION: Karaoke mode is busted on master
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37704 REGRESSION: Karaoke mode is busted on master Change By: Michael Neale You cannot stop karaoke by scrolling up or clicking on the log. It just keeps taking you to the bottom of the page. Additionally, clicking back on a completed run sometimes shows a step in non completed step (see attached). The project I used to reproduce this: https://github.com/kzantow/failure-projectThis was ok as of commit: https://github.com/jenkinsci/blueocean-plugin/commit/dc3e155cab3cc15cf472756c5c64ca5a214c731d I believe, so a recent change. I have not triaged it closer to that. 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-37704) REGRESSION: Karaoke mode is busted on master
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37704 REGRESSION: Karaoke mode is busted on master Change By: Michael Neale Attachment: Screen Shot 2016-08-26 at 11.22.35 AM.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-37704) REGRESSION: Karaoke mode is busted on master
Title: Message Title James Dumay created an issue Jenkins / JENKINS-37704 REGRESSION: Karaoke mode is busted on master Issue Type: Bug Assignee: Thorsten Scherler Components: blueocean-plugin Created: 2016/Aug/26 2:53 AM Priority: Blocker Reporter: James Dumay You cannot stop karaoke by scrolling up or clicking on the log. It just keeps taking you to the bottom of the page. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37704) REGRESSION: Karaoke mode is busted on master
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37704 REGRESSION: Karaoke mode is busted on master Change By: James Dumay Sprint: 1.0-beta-1 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-36054) Reload page after hibernate
Title: Message Title James Dumay commented on JENKINS-36054 Re: Reload page after hibernate Tom FENNELLY we had to revert this as it was causing random page refreshes in Chrome and Safari https://github.com/jenkinsci/blueocean-plugin/pull/435/commits 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-36054) Reload page after hibernate
Title: Message Title James Dumay updated JENKINS-36054 Jenkins / JENKINS-36054 Reload page after hibernate Change By: James Dumay Status: In Review 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-36054) Reload page after hibernate
Title: Message Title James Dumay updated JENKINS-36054 Jenkins / JENKINS-36054 Reload page after hibernate Change By: James Dumay Status: Closed In 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-27121) Make testng.Publisher a SimpleBuildStep
Title: Message Title Jesse Glick commented on JENKINS-27121 Re: Make testng.Publisher a SimpleBuildStep Bullhorn RelEng look under step for now, pending addition of a proper @Symbol. 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-36133) Animate in steps when stage node is clicked
Title: Message Title James Dumay updated JENKINS-36133 Jenkins / JENKINS-36133 Animate in steps when stage node is clicked Change By: James Dumay Status: In Review 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-36133) Animate in steps when stage node is clicked
Title: Message Title James Dumay updated JENKINS-36133 Jenkins / JENKINS-36133 Animate in steps when stage node is clicked Change By: James Dumay Status: Resolved In 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-37682) Unable to download GIT plugin of Jenkins thru Tomcat 7
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-37682 Unable to download GIT plugin of Jenkins thru Tomcat 7 Change By: Mark Waite 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-37682) Unable to download GIT plugin of Jenkins thru Tomcat 7
Title: Message Title Mark Waite resolved as Not A Defect Please don't use bug reports to request help with configuration or installation issues. There are very few people who read bug reports. Please use the jenkins users mailing list for configuration and installation questions. Jenkins / JENKINS-37682 Unable to download GIT plugin of Jenkins thru Tomcat 7 Change By: Mark Waite 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.
[JIRA] (JENKINS-37703) Copy entire tree containing jobs within nested CloudBees Folders
Title: Message Title
Andrew Gray updated an issue
Jenkins / JENKINS-37703
Copy entire tree containing jobs within nested CloudBees Folders
Change By:
Andrew Gray
I have Cloudbees Folder called REL1.5 sitting at the root of Jenkins. This folder contains nested folders which contains jobs. I wish to COPY the entire tree to REL2.0 (which doesn't exist yet).If I add the build step and type ../../REL1.5 in the Copy From field it ls listed which indicates to me that it is found.When I run the job I get the following error: {code:java}Copying /REL1.5 to ../../REL2.0Error: Item '/REL1.5 'was not found.Build step 'Copy Job' marked build as failure{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
[JIRA] (JENKINS-37703) Copy entire tree containing jobs within nested CloudBees Folders
Title: Message Title Andrew Gray created an issue Jenkins / JENKINS-37703 Copy entire tree containing jobs within nested CloudBees Folders Issue Type: Bug Assignee: Unassigned Components: jobcopy-builder-plugin Created: 2016/Aug/26 12:58 AM Environment: Jenkins 2.19, Window 2012 R2, Job Copy Builder plugin 1.4 Priority: Blocker Reporter: Andrew Gray I have Cloudbees Folder called REL1.5 sitting at the root of Jenkins. This folder contains nested folders which contains jobs. I wish to COPY the entire tree to REL2.0 (which doesn't exist yet). If I type ../../REL1.5 in the Copy From field it ls listed which indicates to me that it is found. When I run the job I get the following error: Copying /REL1.5 to ../../REL2.0 Error: Item '/REL1.5 'was not found. Build step 'Copy Job' marked build as failure
[JIRA] (JENKINS-31155) Workflow shared library improvements
Title: Message Title Jesse Glick commented on JENKINS-31155 Re: Workflow shared library improvements Implementation ready. Includes all mandatory requirements specified above, and all optional requirements except the dynamic library step (see discussion above), and ability to load libraries from a non-SCM repository. 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 Jesse Glick updated JENKINS-31155 Jenkins / JENKINS-31155 Workflow shared library improvements 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-37492) Propose adding `diff` utility step
Title: Message Title Michael Neale commented on JENKINS-37492 Re: Propose adding `diff` utility step Ron Dagostino right - well that would be far easier to do as a step I think, or global var lib. 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-37701) Manual trigger not running in build pipeline
Title: Message Title Paul Cleary updated an issue Jenkins / JENKINS-37701 Manual trigger not running in build pipeline Change By: Paul Cleary Environment: Jenkins 2. 19 8 , Build Pipeline Plugin 1.5.3.1 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-37492) Propose adding `diff` utility step
Title: Message Title Ron Dagostino commented on JENKINS-37492 Re: Propose adding `diff` utility step Thanks, Patrick Wolf, for the FilePath vs. FIle info. I have also confirmed that the shared global library code is trusted implicitly in recent versions as per https://issues.jenkins-ci.org/browse/JENKINS-34650, so yes, it would be possible to simply write the script and share it at https://github.com/jenkinsci/pipeline-examples/tree/master/global-library-examples. I will do so if I end up writing it. Michael Neale, I am personally interested in a simple "are two files the same?" step, not full diff functionality. 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-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title James Dumay commented on JENKINS-37323 Re: Ensure that Pipeline Graph can handle stage blocks Yes please ignore them for the time being. I am hoping that we will have nesting disabled until we can sort out the visualisation. 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-37673) Running status indicator is clipped on favourite card
Title: Message Title James Dumay commented on JENKINS-37673 Re: Running status indicator is clipped on favourite card @cliffmeyers thats right the right hand side of the indicator is clipped 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-37673) Running status indicator is clipped on favourite card
Title: Message Title James Dumay edited a comment on JENKINS-37673 Re: Running status indicator is clipped on favourite card @ [~ cliffmeyers ] thats right the right hand side of the indicator is clipped 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-37700) Allow base path to be set for changelog
Title: Message Title Keith Collison resolved as Fixed Jenkins / JENKINS-37700 Allow base path to be set for changelog Change By: Keith Collison 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-37699) Allow expressions in configuration fields
Title: Message Title Keith Collison resolved as Fixed Jenkins / JENKINS-37699 Allow expressions in configuration fields Change By: Keith Collison 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-37700) Allow base path to be set for changelog
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37700 Re: Allow base path to be set for changelog Code changed in jenkins User: propspero238 Path: src/main/java/org/jenkinsci/plugins/liquibase/evaluator/AbstractLiquibaseBuilder.java src/main/java/org/jenkinsci/plugins/liquibase/evaluator/ChangesetEvaluator.java src/main/java/org/jenkinsci/plugins/liquibase/evaluator/FilePathAccessor.java src/main/java/org/jenkinsci/plugins/liquibase/evaluator/RollbackBuildStep.java src/main/resources/org/jenkinsci/plugins/liquibase/evaluator/AbstractLiquibaseBuilder/liquibase-common-config.jelly src/main/webapp/help-basePath.html src/test/java/org/jenkinsci/plugins/liquibase/evaluator/FilePathAccessorTest.java src/test/java/org/jenkinsci/plugins/liquibase/integration/ChangesetEvaluatorBuildResultTest.java src/wiki/confluence.txt http://jenkins-ci.org/commit/liquibase-runner-plugin/8cbb4930083eb4e2e1b07b5da7cee06050a0b12a Log: JENKINS-37700 allow base path to be defined to located changelog file. 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-35836) Stage graph needs to cope with steps at the stage level at the same time as parallel
Title: Message Title James Dumay stopped work on JENKINS-35836 Change By: James Dumay 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-36684) Remove "scroll to item" feature in Activity, Branches and PR tabs
Title: Message Title James Dumay stopped work on JENKINS-36684 Change By: James Dumay 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-35856) JDL component for Dialog
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35856 JDL component for Dialog Change By: James Dumay Sprint: 1.0-beta- 2 1 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-37700) Allow base path to be set for changelog
Title: Message Title Keith Collison updated an issue Jenkins / JENKINS-37700 Allow base path to be set for changelog Change By: Keith Collison Environment: Liquibase Runner Plugin 1.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-37699) Allow expressions in configuration fields
Title: Message Title Keith Collison updated an issue Jenkins / JENKINS-37699 Allow expressions in configuration fields Change By: Keith Collison Environment: Liquibase Runner Plugin 1.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-35501) GIT .gitattributes - line feed configuration not work
Title: Message Title Gavin Kingsley commented on JENKINS-35501 Re: GIT .gitattributes - line feed configuration not work An observation on priority: if I can't get my source code (in the form I need) I can't build my product. I would have thought this issue was core to the mission of Jenkins. 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-22068) Clicking "Build Now" on Promotion causes hanging promotion and requires Jenkins restart
Title: Message Title Kevin Yu commented on JENKINS-22068 Re: Clicking "Build Now" on Promotion causes hanging promotion and requires Jenkins restart Seeing the exact issue on Jenkins ver. 2.17 Plugin 2.27 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-37702) Unbuilt pipelines show up as unknown if favourited
Title: Message Title James Dumay created an issue Jenkins / JENKINS-37702 Unbuilt pipelines show up as unknown if favourited Issue Type: Task Assignee: Unassigned Attachments: Cards.png, Jenkins Blue Ocean 2016-08-26 07-58-27.png Components: blueocean-plugin Created: 2016/Aug/25 10:06 PM Priority: Trivial Reporter: James Dumay Should be styled like the grey bar Add Comment
[JIRA] (JENKINS-37699) Allow expressions in configuration fields
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37699 Re: Allow expressions in configuration fields Code changed in jenkins User: propspero238 Path: pom.xml src/main/java/org/jenkinsci/plugins/liquibase/common/LiquibaseProperty.java src/main/java/org/jenkinsci/plugins/liquibase/common/PropertiesAssembler.java src/main/java/org/jenkinsci/plugins/liquibase/evaluator/AbstractLiquibaseBuilder.java src/main/java/org/jenkinsci/plugins/liquibase/evaluator/ChangesetEvaluator.java src/main/java/org/jenkinsci/plugins/liquibase/evaluator/RollbackBuildStep.java src/test/java/org/jenkinsci/plugins/liquibase/common/PropertiesAssemblerTest.java src/test/java/org/jenkinsci/plugins/liquibase/evaluator/AbstractLiquibaseBuilderTest.java src/test/java/org/jenkinsci/plugins/liquibase/integration/ChangesetEvaluatorBuildResultTest.java http://jenkins-ci.org/commit/liquibase-runner-plugin/e4bfd70b3777bbdb0332921421172848ddfcf2cc Log: JENKINS-37699: Allow expressions in configuration fields. General cleanup of properties assemblage 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-37701) Manual trigger not running in build pipeline
Title: Message Title Paul Cleary created an issue Jenkins / JENKINS-37701 Manual trigger not running in build pipeline Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 2016/Aug/25 9:39 PM Environment: Jenkins 2.19, Build Pipeline Plugin 1.5.3.1 Priority: Minor Reporter: Paul Cleary We are using Folders to manage our build jobs. The folder structure looks like: Denis/ So, it is only one level deep. I am trying to setup a build pipeline. I used the Post Build Action of a "Build other projects (manual)" step. I set the name of the project to use the folder structure: /Denis/job-name Everything appears fine in the Build Pipeline View, but when I click on the "manual trigger" icon, it doesn't run. Inspecting the Jenkins log I am seeing: call to /$stapler/bound/02d15e0b-6aab-4b6d-9c5b-9b7d4ea028f4/triggerManualBuild failed java.lang.IllegalStateException: No upstream trigger found for this projectDenis » denis-publish-portal at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.triggerBuild(BuildPipelineView.java:496) at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.triggerManualBuild(BuildPipelineView.java:405) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[JIRA] (JENKINS-37700) Allow base path to be set for changelog
Title: Message Title Keith Collison created an issue Jenkins / JENKINS-37700 Allow base path to be set for changelog Issue Type: New Feature Assignee: Keith Collison Components: liquibase-runner-plugin Created: 2016/Aug/25 9:39 PM Priority: Minor Reporter: Keith Collison If the changelog file is contained in directory "src/main/resources", for example, the plugin should be allowed to describe that directory as being the base path. Otherwise, the DATABASECHANGELOG table will contain the directory path. Add Comment
[JIRA] (JENKINS-26845) Security: HipChat Plugin can leak global hipchat server host name and token
Title: Message Title aldaris commented on JENKINS-26845 Re: Security: HipChat Plugin can leak global hipchat server host name and token Kurt Madel I believe you are looking for JENKINS-27303. 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-27121) Make testng.Publisher a SimpleBuildStep
Title: Message Title Bullhorn RelEng commented on JENKINS-27121 Re: Make testng.Publisher a SimpleBuildStep Jesse Glick, on Jenkins 2.7, Pipeline 2.2, and testng-plugin 1.14, I don't see any examples in the Snippet Generator to publish the test reports. 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-34123) multi-branch custom branch ordering
Title: Message Title Jesse Glick resolved as Cannot Reproduce There is already a separate view for PRs. Jenkins / JENKINS-34123 multi-branch custom branch ordering Change By: Jesse Glick Status: Open Resolved 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-36849) Github organization folder plugin fetch timeouts
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-36849 Github organization folder plugin fetch timeouts Change By: Jesse Glick Status: Open 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...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35379) gerrit-trigger no longer triggers build
Title: Message Title Eric Barrera commented on JENKINS-35379 Re: gerrit-trigger no longer triggers build I'm seeing the same issue on 2.22 with Jenkins 2.7.2, specifically we saw the problem only when using a dynamic trigger. We host the dynamic trigger file in an Apache server. 2.20 worked, 2.22 didn't. The non-dynamic trigger option worked okay though. 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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title
Scott Crooks edited a comment on JENKINS-34876
Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
[~ganthore] We currently "solve" the problem by doing essentially what you suggested at build time using a pipeline stage:{code:java}parallel ( getRepo1Tags: { sh("git ls-remote --quiet --tags --heads ${repo1GitUrl} | awk '{print \$2}' | grep -vi '{}' | cut -d/ -f1,2 --complement > ${repo1TmpTags}") }, getRepo2Tags: { sh("git ls-remote --quiet --tags --heads ${ repo1GitUrl repo2GitUrl } | awk '{print \$2}' | grep -vi '{}' | cut -d/ -f1,2 --complement > ${repo2TmpTags}") }){code}After that we use the "input" command in pipeline to pause the build and wait for user input.{code:java}def listofRepo1TagsBranches = readFile(repo1TmpTags).trim()def repo1TagBranch = input([message: 'Select a Git branch / tag', parameters: [[$class: 'ChoiceParameterDefinition', choices: listofRepo1TagsBranches, description: '', name: 'Repo 1 branch / tag to build']]])def listofRepo2TagsBranches = readFile(repo2TmpTags).trim()def repo2TagBranch = input([message: 'Select a Git branch / tag', parameters: [[$class: 'ChoiceParameterDefinition', choices: listofRepo2TagsBranches, description: '', name: 'Repo 2 branch / tag to build']]]){code}This works if you're not using automated deployments. However, for our staging environments, we rely on a webhook to be called so that code is automatically pushed to staging. I'm not sure how you would parameterize this _without_ this plugin getting updated for pipeline support. Anyway, I'll figure out another solution in the meantime.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title
Scott Crooks edited a comment on JENKINS-34876
Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
[~ganthore] We currently "solve" the problem by doing essentially what you suggested at build time using a pipeline stage: {code:java} parallel ( getRepo1Tags: { sh("git ls-remote --quiet --tags --heads ${repo1GitUrl} | awk '{print \$2}' | grep -vi '{}' | cut -d/ -f1,2 --complement > ${repo1TmpTags}") }, getRepo2Tags: { sh("git ls-remote --quiet --tags --heads ${repo1GitUrl} | awk '{print \$2}' | grep -vi '{}' | cut -d/ -f1,2 --complement > ${repo2TmpTags}") }) {code} After that we use the "input" command in pipeline to pause the build and wait for user input. {code:java} def listofRepo1TagsBranches = readFile(repo1TmpTags).trim()def repo1TagBranch = input([message: 'Select a Git branch / tag', parameters: [[$class: 'ChoiceParameterDefinition', choices: listofRepo1TagsBranches, description: '', name: 'Repo 1 branch / tag to build']]])def listofRepo2TagsBranches = readFile(repo2TmpTags).trim()def repo2TagBranch = input([message: 'Select a Git branch / tag', parameters: [[$class: 'ChoiceParameterDefinition', choices: listofRepo2TagsBranches, description: '', name: 'Repo 2 branch / tag to build']]]) {code} This works if you're not using automated deployments. However, for our staging environments, we rely on a webhook to be called so that code is automatically pushed to staging. I'm not sure how you would parameterize this _without_ this plugin getting updated for pipeline support. Anyway, I'll figure out another solution in the meantime.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title
Scott Crooks commented on JENKINS-34876
Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Mark Austin We currently "solve" the problem by doing essentially what you suggested at build time using a pipeline stage: parallel ( getRepo1Tags: { sh("git ls-remote --quiet --tags --heads $ {repo1GitUrl} | awk '{print \$2}' | grep -vi '{}' | cut -d/ -f1,2 --complement > ${repo1TmpTags}") }, getRepo2Tags: { sh("git ls-remote --quiet --tags --heads ${repo1GitUrl} | awk ' {print \$2} ' | grep -vi '{}' | cut -d/ -f1,2 --complement > $ {repo2TmpTags} ") } ) After that we use the "input" command in pipeline to pause the build and wait for user input. def listofRepo1TagsBranches = readFile(repo1TmpTags).trim() def repo1TagBranch = input([message: 'Select a Git branch / tag', parameters: [[$class: 'ChoiceParameterDefinition', choices: listofRepo1TagsBranches, description: '', name: 'Repo 1 branch / tag to build']]]) def listofRepo2TagsBranches = readFile(repo2TmpTags).trim() def repo2TagBranch = input([message: 'Select a Git branch / tag', parameters: [[$class: 'ChoiceParameterDefinition', choices: listofRepo2TagsBranches, description: '', name: 'Repo 2 branch / tag to build']]]) This works if you're not using automated deployments. However, for our staging environments, we rely on a webhook to be called so that code is automatically pushed to staging. I'm not sure how you would parameterize this without this plugin getting updated for pipeline support. Anyway, I'll figure out another solution in the meantime.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this
[JIRA] (JENKINS-37699) Allow expressions in configuration fields
Title: Message Title
Keith Collison created an issue
Jenkins / JENKINS-37699
Allow expressions in configuration fields
Issue Type:
New Feature
Assignee:
Keith Collison
Components:
liquibase-runner-plugin
Created:
2016/Aug/25 8:32 PM
Priority:
Minor
Reporter:
Keith Collison
Tokens like "$ {changelogFile} " should be able to be resolved to a value within the environment.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36974) Developer can stop a run from the activity tab
Title: Message Title Cliff Meyers started work on JENKINS-36974 Change By: Cliff Meyers 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-37673) Running status indicator is clipped on favourite card
Title: Message Title Cliff Meyers commented on JENKINS-37673 Re: Running status indicator is clipped on favourite card Actually I think it's more that the right edge is clipped, no? 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-37673) Running status indicator is clipped on favourite card
Title: Message Title Cliff Meyers commented on JENKINS-37673 Re: Running status indicator is clipped on favourite card James Dumay I am admittedly squinting at my screen trying to see what's wrong The circle looks normal to me, are you saying the left edge is clipped? 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-30183) Openstack Cloud Plugin does not wait until the user data script completes
Title: Message Title Donald Morton commented on JENKINS-30183 Re: Openstack Cloud Plugin does not wait until the user data script completes How do you control when cloud-init creates a user? 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-37698) Folders support for Stash plugin
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-37698 Folders support for Stash plugin Issue Type: Improvement Assignee: nathan m Components: stash-pullrequest-builder-plugin Created: 2016/Aug/25 8:10 PM Priority: Minor Reporter: Dan Tranter We have several teams using the Stash PR plugin on a single Jenkins master. It would be helpful to allow them to specify the repo they should connect to at the Folder level (restricting items in a Folder, owned/managed by a specific team), and not just the master configuration (where same behaviour applies to all teams/users). However, if there are security reasons this shouldn't be done, please ignore this request. Add Comment
[JIRA] (JENKINS-26799) Multiple SCMs plugin support
Title: Message Title Boguslaw Klimas commented on JENKINS-26799 Re: Multiple SCMs plugin support Nikolas Falco This is very good POC but You may not have defined SCM when you add parameter or SCM definition can change after add parameter. Then you not have the actual information about SCM in parameter definition. I think good and simple solution is a: Add two option: MultipleSCM: FIRST, ALL, MATCH_REPOSITORY_URL (combo) MultipleSCM Url: __ (text field - regexp) 'FIRST' is default value. If you choose 'FIRST' - plugin will take data from first defined SCM (git repository) 'ALL' plugin take data from all defined SCM 'MATCH_REPOSITORY_URL' plugin will take data from all SCM which url match from regular _expression_. The advantage of this solution is: you do not need know about defined SCM. and this and this is more flexible solution. Regards Boguslaw 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-37697) Folders support for Rally plugin
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-37697 Folders support for Rally plugin Issue Type: Improvement Assignee: Unassigned Components: rally-plugin Created: 2016/Aug/25 8:06 PM Priority: Minor Reporter: Dan Tranter We have several teams using the Rally plugin on a single Jenkins master. Currently the Rally plugin must be customized for a given SCM at global config level (preventing it's customization in multi-team scenario). It would be nice to configure or override the settings at Folder level (restricting items in a Folder and below) Add Comment
[JIRA] (JENKINS-37696) Folders support for Green Balls
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-37696 Folders support for Green Balls Issue Type: Improvement Assignee: asgeirn Components: greenballs-plugin Created: 2016/Aug/25 7:59 PM Priority: Minor Reporter: Dan Tranter We have several teams using the Green Balls plugin on a single Jenkins master. It would be helpful to allow the features to be customized at the Folder level (restricting items in a Folder and below), and not just the master configuration - where the changes affect everyone and all projects. Add Comment
[JIRA] (JENKINS-37695) Folders support for publish-over-ssh
Title: Message Title Dan Tranter updated an issue Jenkins / JENKINS-37695 Folders support for publish-over-ssh Change By: Dan Tranter Priority: Major Minor 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-37695) Folders support for publish-over-ssh
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-37695 Folders support for publish-over-ssh Issue Type: Improvement Assignee: bap Components: publish-over-ssh-plugin Created: 2016/Aug/25 7:55 PM Priority: Major Reporter: Dan Tranter We have several teams using the Publish over ssh plugin on a single Jenkins master. It would be helpful to allow them to specify the server information they should connect to at the Folder level (restricting items in a Folder, for limit of access/security best practices), and not just the master configuration (where everything is visible to everyone). However, if there are security reasons this shouldn't be done, please ignore this request. Add Comment
[JIRA] (JENKINS-37690) Try blow up react
Title: Message Title Cliff Meyers commented on JENKINS-37690 Re: Try blow up react Might be a good place to start: https://github.com/search?o=desc=react=stars=Repositories=%E2%9C%93 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-28119) Link to log of failed step
Title: Message Title Leah Klearman commented on JENKINS-28119 Re: Link to log of failed step I'm interested in ensuring that the solution works with a parallel() that has a large number of sub-jobs...that all of the jobs get completed and multiple failures can be identified. 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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title
Mark Austin edited a comment on JENKINS-34876
Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Hey Scott,I guess we could just run a script like this as an alternative on the Jenkins master so that the main workspace has access to the properties file: {code} git ls-remote -t https://github.com/jenkinsci/github-plugin | awk '{print $2}' | cut -d '/' -f 3 | cut -d '^' -f 1 | sort -b -t . -k 1,1nr -k 2,2nr -k 3,3r -k 4,4r -k 5,5r | uniq | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > /tmp/versions.properties {code} That way we don't have to force Jenkins to double checkout the git repo per my older example.There are a number of ways you could do this. The end goal is to make sure that the script runs on a regular basis or immediately after the jenkins workspace has polled the git repo.For instance, you could have the script execute on the jenkins master directly through something as simple as a cron job.Or, you could also try running it with a post-merge git hook in the workspace, that way it runs each time after a "git pull" occurs. Here is a basic example that you could modify for your needs:https://gist.github.com/sindresorhus/7996717If you're familiar with incron (http://inotify.aiken.cz/?section=incron=why=en), you could have that daemon execute the script each time it notices a file change in the git checkout folder on the workspace or just wait for this bug to get patched. :-)Hope this helps...
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
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title
Mark Austin edited a comment on JENKINS-34876
Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Hey Scott, I guess we could just run a script like this as an alternative on the Jenkins master so that the main workspace has access to the properties file:git ls-remote -t https://github.com/jenkinsci/github-plugin | awk '{print $2}' | cut -d '/' -f 3 | cut -d '^' -f 1 | sort -b -t . -k 1,1nr -k 2,2nr -k 3,3r -k 4,4r -k 5,5r | uniq | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > /tmp/versions.propertiesThat way we don't have to force Jenkins to double checkout the git repo per my older example. There are a number of ways you could do this. The end goal is to make sure that the script runs on a regular basis or immediately after the jenkins workspace has polled the git repo.For instance, you could have the script execute on the jenkins master directly through something as simple as a cron job.Or, you could also try running it with a post-merge git hook in the workspace, that way it runs each time after a "git pull" occurs. Here is a basic example that you could modify for your needs:https://gist.github.com/sindresorhus/7996717If you're familiar with incron (http://inotify.aiken.cz/?section=incron=why=en), you could have that daemon execute the script each time it notices a file change in the git checkout folder on the workspace or just wait for this bug to get patched. :-)Hope this helps...
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
[JIRA] (JENKINS-37694) link to archived build artifacts is hidden until pipeline has finished
Title: Message Title
Leah Klearman created an issue
Jenkins / JENKINS-37694
link to archived build artifacts is hidden until pipeline has finished
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2016/Aug/25 7:18 PM
Environment:
Jenkins 2.x, Pipeline job.
Labels:
workflow
Priority:
Minor
Reporter:
Leah Klearman
jglick klrmn: hah. Works fine in stage view, but https://github.com/jenkinsci/jenkins/blob/ee447af7e8e283ff50032532a571766f810ea061/core/src/main/resources/lib/hudson/artifactList.jelly#L44 explicitly hides it during the build, for no reason I can see. Test case: stage 'All'; node {writeFile file: 'f.txt', text: 'hello'; archive 'f.txt'; input 'hold on'} Workaround: manually append `artifact/` to build index URL.
Add Comment
[JIRA] (JENKINS-26799) Multiple SCMs plugin support
Title: Message Title Dakota Brown updated an issue Jenkins / JENKINS-26799 Multiple SCMs plugin support Change By: Dakota Brown Comment: I like the general direction. I'll look closely at it when I get the chance 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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Mark Austin edited a comment on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Hey Scott,There are a number of ways you could do this. The end goal is to make sure that the script runs on a regular basis or immediatley immediately after the slave builder jenkins workspace has polled the git repo.For instance, you could have the script execute on the slave jenkins master directly through something as simple as a cron job.Or, you could also try running it with a post-merge git hook in the workspace , that way it runs each time after a "git pull" occurs. Here is a basic example that you could modify for your needs:https://gist.github.com/sindresorhus/7996717If you're familiar with incron (http://inotify.aiken.cz/?section=incron=why=en), you could have that daemon execute the script each time it notices a file change in the git checkout folder on the slave workspace or just wait for this bug to get patched. :-)Hope this helps... 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-36973) Developer can stop the build on a running card
Title: Message Title Cliff Meyers commented on JENKINS-36973 Re: Developer can stop the build on a running card PR: https://github.com/jenkinsci/blueocean-plugin/pull/430 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-36973) Developer can stop the build on a running card
Title: Message Title Cliff Meyers updated JENKINS-36973 Jenkins / JENKINS-36973 Developer can stop the build on a running card Change By: Cliff Meyers 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-36973) Developer can stop the build on a running card
Title: Message Title Cliff Meyers commented on JENKINS-36973 Re: Developer can stop the build on a running card I altered the "stopping" and "stopped" text slightly so it's worded similarly to how "queued" and "started" work, just for consistency. 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-36660) Acceptance tests for nested project and funky branch name regressions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36660 Re: Acceptance tests for nested project and funky branch name regressions Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineActivity.js src/main/js/page_objects/blueocean/bluePipelineBranch.js src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/main/js/util/url.js src/test/js/edgeCases/folder.js http://jenkins-ci.org/commit/blueocean-acceptance-test/508e97286303b24a94c56d0cfd1d5099d5e32e54 Log: JENKINS-36660 Start test for pressing run button. add test to validate activities. move clickTab and related code to url util class 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-30183) Openstack Cloud Plugin does not wait until the user data script completes
Title: Message Title Joshua Harlow commented on JENKINS-30183 Re: Openstack Cloud Plugin does not wait until the user data script completes Right, I've got another way to do this also, Where basically u make the user that is being used to log-in really late in the cloud-init process. Then the external ssh connection won't be possible until the final user adding has actually happened (which is then after all the other stuff I want to occur has finished). Its not perfect, and as being one of the cloud-init authors this is a known thing; and since this plug-in is not really tying itself to cloud-init tightly the solutions to it become a little bit harder (especially say with windows). 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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Mark Austin commented on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Hey Scott, There are a number of ways you could do this. The end goal is to make sure that the script runs on a regular basis or immediatley after the slave builder has polled the git repo. For instance, you could have the script execute on the slave directly through something as simple as a cron job. Or, you could also try running it with a post-merge git hook, that way it runs each time after a "git pull" occurs. Here is a basic example that you could modify for your needs: https://gist.github.com/sindresorhus/7996717 If you're familiar with incron (http://inotify.aiken.cz/?section=incron=why=en), you could have that daemon execute the script each time it notices a file change in the git checkout folder on the slave. ... or just wait for this bug to get patched. Hope this helps... 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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Scott Crooks edited a comment on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM [~ganthore] Mark ,Can you be a bit more detailed about your job setup? I get that the BASH command you have above will grab the list of tags, and that it will put that in a file, and that the Extended Choice parameter will read that file at build time. What I don't get is when that BASH command is executed? In Jenkins pipeline, there's no option to run a BASH script _before_ the Extended Choice plugin grabs the list of tags. 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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Scott Crooks commented on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Mark Austin Mark, Can you be a bit more detailed about your job setup? I get that the BASH command you have above will grab the list of tags, and that it will put that in a file, and that the Extended Choice parameter will read that file at build time. What I don't get is when that BASH command is executed? In Jenkins pipeline, there's no option to run a BASH script before the Extended Choice plugin grabs the list of tags. 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-26799) Multiple SCMs plugin support
Title: Message Title Dakota Brown commented on JENKINS-26799 Re: Multiple SCMs plugin support I like the general direction. I'll look closely at it when I get the chance 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-26799) Multiple SCMs plugin support
Title: Message Title Dakota Brown commented on JENKINS-26799 Re: Multiple SCMs plugin support I like the general direction. I'll look closely at it when I get the chance 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-36660) Acceptance tests for nested project and funky branch name regressions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36660 Re: Acceptance tests for nested project and funky branch name regressions Code changed in jenkins User: Thorsten Scherler Path: src/test/js/multibranch.js http://jenkins-ci.org/commit/blueocean-acceptance-test/8f8f30dbb4af7041322a2e85a2c4fedaac00d329 Log: JENKINS-36660 make sure we do not start without wait for finish Compare: https://github.com/jenkinsci/blueocean-acceptance-test/compare/1ded7923e7b2...8f8f30dbb4af 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-36660) Acceptance tests for nested project and funky branch name regressions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36660 Re: Acceptance tests for nested project and funky branch name regressions Code changed in jenkins User: Thorsten Scherler Path: src/test/js/log-karaoke/stages.js http://jenkins-ci.org/commit/blueocean-acceptance-test/7da8e076d9bc23d7dc48c7fd38d7cbaf6f8af6d0 Log: JENKINS-36660 fix renamed methood 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-26799) Multiple SCMs plugin support
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-26799
Multiple SCMs plugin support
Change By:
Nikolas Falco
Comment:
This is only a working POC (proof of concept)https://github.com/nfalco79/git-parameter-plugin/tree/feature/JENKINS-26799 !screenshot-1.png|thumbnail! !screenshot-2.png|thumbnail! *It works but*:* here MultiSCM is not an real optional dependency (I do not know if jenkins have some API to avoid Class.forName("") to know if a plugin is installed)* missing test case* missing handle event when you change repo URL and you have not set an SCM name (why if you not set any SCM Name the SCM key it's the string "git " + repoURL)* maybe some faultback for backward compatibility
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-26799) Multiple SCMs plugin support
Title: Message Title
Nikolas Falco commented on JENKINS-26799
Re: Multiple SCMs plugin support
This is only a working POC (proof of concept) https://github.com/nfalco79/git-parameter-plugin/tree/feature/JENKINS-26799 It works but:
here MultiSCM is not an real optional dependency (I do not know if jenkins have some API to avoid Class.forName("") to know if a plugin is installed)
missing test case
missing handle event when you change repo URL and you have not set an SCM name (why if you not set any SCM Name the SCM key it's the string "git " + repoURL)
maybe some faultback for backward compatibility
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-37693) Provide documentation on how to use this plugin in a Jenkins pipeline
Title: Message Title Steve Collins created an issue Jenkins / JENKINS-37693 Provide documentation on how to use this plugin in a Jenkins pipeline Issue Type: Improvement Assignee: Carlos Sanchez Components: docker-build-publish-plugin Created: 2016/Aug/25 5:49 PM Priority: Major Reporter: Steve Collins Create example of using this plugin in a Jenkins 2.x pipeline. Using a pipeline would be very useful when building many docker images Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-26799) Multiple SCMs plugin support
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-26799 Multiple SCMs plugin support Change By: Nikolas Falco Attachment: screenshot-4.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-26799) Multiple SCMs plugin support
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-26799 Multiple SCMs plugin support Change By: Nikolas Falco Attachment: screenshot-3.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-26799) Multiple SCMs plugin support
Title: Message Title
Nikolas Falco commented on JENKINS-26799
Re: Multiple SCMs plugin support
This is only a working POC (proof of concept) https://github.com/nfalco79/git-parameter-plugin/tree/feature/JENKINS-26799 It works but:
here MultiSCM is not an real optional dependency (I do not know if jenkins have some API to avoid Class.forName("") to know if a plugin is installed)
missing test case
missing handle event when you change repo URL and you have not set an SCM name (why if you not set any SCM Name the SCM key it's the string "git " + repoURL)
maybe some faultback for backward compatibility
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-26799) Multiple SCMs plugin support
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-26799 Multiple SCMs plugin support Change By: Nikolas Falco Attachment: screenshot-2.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-26799) Multiple SCMs plugin support
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-26799 Multiple SCMs plugin support Change By: Nikolas Falco 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-36660) Acceptance tests for nested project and funky branch name regressions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36660 Re: Acceptance tests for nested project and funky branch name regressions Code changed in jenkins User: Thorsten Scherler Path: src/test/resources/testResults/Jenkinsfile http://jenkins-ci.org/commit/blueocean-acceptance-test/1ded7923e7b2feeb881bbb757e6b09145ccf9546 Log: JENKINS-36660 remove legacy folder 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.
