[JIRA] [repo-plugin] (JENKINS-22299) Add a way to specify credentials
Title: Message Title Andreas Naumann commented on JENKINS-22299 Re: Add a way to specify credentials Giving this a vote since I desperately need the repo-plugin to be able to use passphrase-protected keys in the the polling phase. Unfortunately the ssh-agent only works in the actual build. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gerrit-trigger-plugin] (JENKINS-35092) No gerrit variables when using gerrit trigger
Title: Message Title Ilya Ashchepkov closed an issue as Duplicate Jenkins / JENKINS-35092 No gerrit variables when using gerrit trigger Change By: Ilya Ashchepkov Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gerrit-trigger-plugin] (JENKINS-35092) No gerrit variables when using gerrit trigger
Title: Message Title Ilya Ashchepkov commented on JENKINS-35092 Re: No gerrit variables when using gerrit trigger Darren Maki thank you for the reply. I will use workaround with -Dhudson.model.ParametersAction.keepUndefinedParameters=true until plugin is not updated. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34532) Change setup wizard 'Website' text label to icon
Title: Message Title Oleg Nenashev commented on JENKINS-34532 Re: Change setup wizard 'Website' text label to icon I doubt this kind of bugs is a subject for backporting Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35114) Reload Configuration donot reload plugin configuration
Title: Message Title Sagayaraj David assigned an issue to Unassigned Jenkins / JENKINS-35114 Reload Configuration donot reload plugin configuration Change By: Sagayaraj David Assignee: Antek Baranski Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35116) Node naming pattern
Title: Message Title Sagayaraj David created an issue Jenkins / JENKINS-35116 Node naming pattern Issue Type: New Feature Assignee: Unassigned Components: core Created: 2016/May/25 5:47 AM Priority: Major Reporter: Sagayaraj David We need to enforce node names to be of certain pattern. Currently this feature is available for Job names only. We need similar pattern enforcement for Node names and View Names. Add Comment
[JIRA] [multiple-scms-plugin] (JENKINS-34962) Multiple SCM plugin not create separate repo manifest.
Title: Message Title Manoj Kumar updated an issue Jenkins / JENKINS-34962 Multiple SCM plugin not create separate repo manifest. Change By: Manoj Kumar Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [parameterized-trigger-plugin] (JENKINS-35024) Parametrized build doesn't set environment variables in Mutli-configuration projects
Title: Message Title Vlad Frolov resolved as Fixed I have updated several plugins today and now it is working fine! Jenkins / JENKINS-35024 Parametrized build doesn't set environment variables in Mutli-configuration projects Change By: Vlad Frolov Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35114) Reload Configuration donot reload plugin configuration
Title: Message Title Sagayaraj David created an issue Jenkins / JENKINS-35114 Reload Configuration donot reload plugin configuration Issue Type: Bug Assignee: Antek Baranski Components: core Created: 2016/May/25 5:33 AM Priority: Major Reporter: Sagayaraj David In Jenkins home there are number of config xml files including core config.xml and many other plugin release configuration files and some of them are below org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin.xml hudson.plugins.sonar.SonarPublisher.xml hudson.tools.JDKInstaller.xml hudson.tasks.Maven.xml hudson.plugins.git.GitTool.xml hudson.plugins.analysis.core.GlobalSettings.xml These files dont get reloaded upon clicking Reload Configuration link, but they get refreshed when restarting Jenkins Add Comment
[JIRA] [core] (JENKINS-35094) unable to use grunt commands
Title: Message Title abhishek chandel updated an issue Jenkins / JENKINS-35094 unable to use grunt commands Change By: abhishek chandel Component/s: nodejs-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35094) unable to use grunt commands
Title: Message Title abhishek chandel updated an issue Jenkins / JENKINS-35094 unable to use grunt commands Change By: abhishek chandel Priority: Critical Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35094) unable to use grunt commands
Title: Message Title abhishek chandel updated an issue Jenkins / JENKINS-35094 unable to use grunt commands Change By: abhishek chandel Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [junit-plugin] (JENKINS-34666) JUnit test durations accounted improperly
Title: Message Title Christopher Head updated an issue Jenkins / JENKINS-34666 JUnit test durations accounted improperly Change By: Christopher Head Environment: Linux amd64, Jenkins v2. 5 6 , jUnit plugin v1.13 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-35104) git plugin still checks out all branches when refspec set
Title: Message Title Mark Waite resolved as Not A Defect As far as I can tell, you're trying to clone a SHA1 whose history does not exist in the target repository because you are using shallow clone. Refer to this superuser.com article for more information on the condition. One work around appears to be to not use shallow clone. Another that might work would be to increase the depth of the shallow clone. Jenkins / JENKINS-35104 git plugin still checks out all branches when refspec set Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-35104) git plugin still checks out all branches when refspec set
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-35104 git plugin still checks out all branches when refspec set Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jira-ext-plugin] (JENKINS-33856) jira-ext-plugin fails to parse commit message for JIRA ticket in certain patterns
Title: Message Title Dan Alvizu resolved as Cannot Reproduce Please re-open with more info if problem persists Jenkins / JENKINS-33856 jira-ext-plugin fails to parse commit message for JIRA ticket in certain patterns Change By: Dan Alvizu Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jira-ext-plugin] (JENKINS-33054) "Update a Field" does not work with environment variables
Title: Message Title Dan Alvizu resolved as Fixed Jenkins / JENKINS-33054 "Update a Field" does not work with environment variables Change By: Dan Alvizu Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jira-ext-plugin] (JENKINS-33054) "Update a Field" does not work with environment variables
Title: Message Title Dan Alvizu commented on JENKINS-33054 Re: "Update a Field" does not work with environment variables Added support for environment variables in field, label, fix version, and single ticket strategy https://github.com/jenkinsci/jira-ext-plugin/commit/d4995e8b61a34c740f04048b47e5ca63c16a4435 Fixed in jira-ext 0.5 release - should be available in about 4 hours Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jira-ext-plugin] (JENKINS-33054) "Update a Field" does not work with environment variables
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33054 Re: "Update a Field" does not work with environment variables Code changed in jenkins User: Dan Alvizu Path: src/main/java/org/jenkinsci/plugins/jiraext/view/AddFixVersion.java src/main/java/org/jenkinsci/plugins/jiraext/view/AddLabel.java src/main/java/org/jenkinsci/plugins/jiraext/view/SingleTicketStrategy.java src/main/java/org/jenkinsci/plugins/jiraext/view/UpdateField.java src/test/java/org/jenkinsci/plugins/jiraext/view/AddFixVersionTest.java src/test/java/org/jenkinsci/plugins/jiraext/view/AddLabelTest.java src/test/java/org/jenkinsci/plugins/jiraext/view/SingleTicketStrategyTest.java src/test/java/org/jenkinsci/plugins/jiraext/view/UpdateFieldTest.java http://jenkins-ci.org/commit/jira-ext-plugin/d4995e8b61a34c740f04048b47e5ca63c16a4435 Log: JENKINS-33054 support environment variables in fix version, label, field, and single ticket strategy Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-oauth-plugin] (JENKINS-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title
Dominic Scheirlinck commented on JENKINS-34775
Re: Broken jobs after upgrade to 1.651.2 security update
Sam Gleske I've prepared a patch at https://github.com/jenkinsci/github-oauth-plugin/pull/56 - it looks like the problem is just a bad assumption/cast to GithubAuthenticationToken, and the fix just adds an `instanceof` check. I don't think I have to convert the UserPasswordAuthenticationToken as well (just bailing out of loadUserByUsername works fine for me).
Roberto Sanchez That's an unrelated error ("LDAP: error code 1 - 2020: Operation unavailable without authentication") from your LDAP server. Please start a new issue.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [extended-choice-parameter-plugin] (JENKINS-35047) Delimiter missing from Multi-level Multi Select
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35047 Re: Delimiter missing from Multi-level Multi Select Code changed in jenkins User: vimil Path: src/main/java/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition.java http://jenkins-ci.org/commit/extended-choice-parameter-plugin/a53c9d92ec1f88f8b756f308343d3cb1b20b61e7 Log: fixing JENKINS-35047 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jira-ext-plugin] (JENKINS-33856) jira-ext-plugin fails to parse commit message for JIRA ticket in certain patterns
Title: Message Title Dan Alvizu commented on JENKINS-33856 Re: jira-ext-plugin fails to parse commit message for JIRA ticket in certain patterns I've added a test for your issue: https://github.com/jenkinsci/jira-ext-plugin/commit/866012f9a4ea39c1c2ce8a0f2dbaa729f6bb3876 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title
Shah Chowdhury updated an issue
Jenkins / JENKINS-35113
Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Change By:
Shah Chowdhury
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color}Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present.Again, {color: red}{color: # d04437 14892c }*Works fine in Jenkins 1.651.1*{color} {color}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title
Shah Chowdhury updated an issue
Jenkins / JENKINS-35113
Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Change By:
Shah Chowdhury
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color}Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present.Again, {color:red} {color:#d04437} *Works fine in Jenkins 1.651.1*{color} {color}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [jira-ext-plugin] (JENKINS-33856) jira-ext-plugin fails to parse commit message for JIRA ticket in certain patterns
Title: Message Title
Dan Alvizu edited a comment on JENKINS-33856
Re: jira-ext-plugin fails to parse commit message for JIRA ticket in certain patterns
Hi there! Owner here - I'm not able to reproduce. Can you please go to {{/configure}} and check that you have 'Ticket Pattern' configured to match the issue keys you are trying to search for? (e.g, {{SBUSWIT-}}).If yes, and the problem persists, please include the following to help me debug:* the job's config.xml* the job run's build.xml* the full console log * issue pattern specified in global config Thanks!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title
Shah Chowdhury updated an issue
Jenkins / JENKINS-35113
Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Change By:
Shah Chowdhury
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color}Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present.Again, {color: #14892c red }*Works fine in Jenkins 1.651.1*{color}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title
Shah Chowdhury updated an issue
Jenkins / JENKINS-35113
Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Change By:
Shah Chowdhury
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color}Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present.Again, * {color:#14892c} * Works fine in Jenkins 1.651.1 * {color} *
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties' in 'Parameterized Trigger' plugin
Title: Message Title Shah Chowdhury updated an issue Jenkins / JENKINS-35113 Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties' in 'Parameterized Trigger' plugin Change By: Shah Chowdhury Summary: Upgrade to 1.651.2 or 2.6.x broke breaks 'Parameters from properties' in 'Parameterized Trigger' plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [parameterized-trigger-plugin] (JENKINS-35113) Upgrade to 1.651.2 or 2.6.x broke 'Parameters from properties' in 'Parameterized Trigger' plugin
Title: Message Title Shah Chowdhury created an issue Jenkins / JENKINS-35113 Upgrade to 1.651.2 or 2.6.x broke 'Parameters from properties' in 'Parameterized Trigger' plugin Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2016/May/25 2:28 AM Environment: Jenkins 1.651.2 or 2.6 Parameterized Trigger Plugin 2.30 Priority: Critical Reporter: Shah Chowdhury Works in Jenkins 1.651.1 Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties' in 'Parameterized Trigger' plugin. Steps to recreate: Create two Jenkins projects: proj1 and proj2 In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file Build proj1 which should trigger proj2
[JIRA] [jira-ext-plugin] (JENKINS-33856) jira-ext-plugin fails to parse commit message for JIRA ticket in certain patterns
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33856 Re: jira-ext-plugin fails to parse commit message for JIRA ticket in certain patterns Code changed in jenkins User: Dan Alvizu Path: src/test/java/org/jenkinsci/plugins/jiraext/view/MentionedInCommitStrategyTest.java http://jenkins-ci.org/commit/jira-ext-plugin/866012f9a4ea39c1c2ce8a0f2dbaa729f6bb3876 Log: Add test for JENKINS-33856 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pipeline-stage-view-plugin] (JENKINS-33498) Improve full screen view of pipeline stage view
Title: Message Title John Ament commented on JENKINS-33498 Re: Improve full screen view of pipeline stage view Sam, Thanks, this is definitely better but could still use some work. Right now, the graphical component is the same size on both the job and full screen view. Is it possible for the component itself to reach 100% width? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-32761) support multiple unshelve changelists in one build step
Title: Message Title
dan tran commented on JENKINS-32761
Re: support multiple unshelve changelists in one build step
I wonder if the change is as simple as this? at UnshelveBuilder
// Expand shelf $ {VAR}
as needed and set as LABEL String ids = ws.getExpand().format(shelf, false);
String [] tokens = StringUtils.split( id ); for ( String id: tokens ) { int change = Integer.parseInt(id); task.setShelf(change); task.setWorkspace(ws); if ( !buildWorkspace.act(task) ) { return false; }
}
return true;
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-34997) Add a Text Array Parameter to Parameterized Build
Title: Message Title
Matthew Kruer edited a comment on JENKINS-34997
Re: Add a Text Array Parameter to Parameterized Build
{{ If using Text_Parameter without line quotesIp1 file1 file2 file3Ip2 file3 file4Ip3 file2 file4 file5 file6for a in ${!Text_Parameter[@]}; do echo ${Text_Parameter[$a]} done+ for a in '${!Text_Parameter[@]}'+ echo Ip1 file1 file2 file3 Ip2 file3 file4 Ip3 file2 file4 file5 file6Ip1 file1 file2 file3 Ip2 file3 file4 Ip3 file2 file4 file5 file6If using Text_Parameter with line quotes'Ip1 file1 file2 file3''Ip2 file3 file4''Ip3 file2 file4 file5 file6'for a in ${!Text_Parameter[@]}; do echo ${Text_Parameter[$a]} done+ for a in '${!Text_Parameter[@]}'+ echo ''\''Ip1' file1 file2 'file3'\''' ''\''Ip2' file3 'file4'\''' ''\''Ip3' file2 file4 file5 'file6'\Ip1 file1 file2 file3' 'Ip2 file3 file4' 'Ip3 file2 file4 file5 file6'Text_Array_Parameter=( 'Ip1 file1 file2 file3''Ip2 file3 file4''Ip3 file2 file4 file5 file6' )for b in ${!Text_Array_Parameter[@]}; do echo ${Text_Array_Parameter[$b]} done+ Text_Array_Parameter=('Ip1 file1 file2 file3' 'Ip2 file3 file4' 'Ip3 file2 file4 file5 file6')+ for b in '${!Text_Array_Parameter[@]}'+ echo Ip1 file1 file2 file3Ip1 file1 file2 file3+ for b in '${!Text_Array_Parameter[@]}'+ echo Ip2 file3 file4Ip2 file3 file4+ for b in '${!Text_Array_Parameter[@]}'+ echo Ip3 file2 file4 file5 file6Ip3 file2 file4 file5 file6So there is definitely something going on in the in the shell script where it is loosing something in the process. }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-34997) Add a Text Array Parameter to Parameterized Build
Title: Message Title
Matthew Kruer edited a comment on JENKINS-34997
Re: Add a Text Array Parameter to Parameterized Build
{{ If using Text_Parameter without line quotesIp1 file1 file2 file3Ip2 file3 file4Ip3 file2 file4 file5 file6for a in ${!Text_Parameter[@]}; do echo ${Text_Parameter[$a]} done+ for a in '${!Text_Parameter[@]}'+ echo Ip1 file1 file2 file3 Ip2 file3 file4 Ip3 file2 file4 file5 file6Ip1 file1 file2 file3 Ip2 file3 file4 Ip3 file2 file4 file5 file6If using Text_Parameter with line quotes'Ip1 file1 file2 file3''Ip2 file3 file4''Ip3 file2 file4 file5 file6'for a in ${!Text_Parameter[@]}; do echo ${Text_Parameter[$a]} done+ for a in '${!Text_Parameter[@]}'+ echo ''\''Ip1' file1 file2 'file3'\''' ''\''Ip2' file3 'file4'\''' ''\''Ip3' file2 file4 file5 'file6'\Ip1 file1 file2 file3' 'Ip2 file3 file4' 'Ip3 file2 file4 file5 file6'Text_Array_Parameter=( 'Ip1 file1 file2 file3''Ip2 file3 file4''Ip3 file2 file4 file5 file6' )for b in ${!Text_Array_Parameter[@]}; do echo ${Text_Array_Parameter[$b]} done+ Text_Array_Parameter=('Ip1 file1 file2 file3' 'Ip2 file3 file4' 'Ip3 file2 file4 file5 file6')+ for b in '${!Text_Array_Parameter[@]}'+ echo Ip1 file1 file2 file3Ip1 file1 file2 file3+ for b in '${!Text_Array_Parameter[@]}'+ echo Ip2 file3 file4Ip2 file3 file4+ for b in '${!Text_Array_Parameter[@]}'+ echo Ip3 file2 file4 file5 file6Ip3 file2 file4 file5 file6So there is definitely something going on in the in the shell script where it is loosing something in the process. }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-34997) Add a Text Array Parameter to Parameterized Build
Title: Message Title
Matthew Kruer commented on JENKINS-34997
Re: Add a Text Array Parameter to Parameterized Build
If using Text_Parameter without line quotes Ip1 file1 file2 file3 Ip2 file3 file4 Ip3 file2 file4 file5 file6
for a in $ {!Text_Parameter[@]}; do echo ${Text_Parameter[$a]} done + for a in '${!Text_Parameter[@]}
' + echo Ip1 file1 file2 file3 Ip2 file3 file4 Ip3 file2 file4 file5 file6 Ip1 file1 file2 file3 Ip2 file3 file4 Ip3 file2 file4 file5 file6
If using Text_Parameter with line quotes 'Ip1 file1 file2 file3' 'Ip2 file3 file4' 'Ip3 file2 file4 file5 file6'
for a in $ {!Text_Parameter[@]}; do echo ${Text_Parameter[$a]} done + for a in '${!Text_Parameter[@]}
' + echo ''\''Ip1' file1 file2 'file3'\''' ''\''Ip2' file3 'file4'\''' ''\''Ip3' file2 file4 file5 'file6'\''' 'Ip1 file1 file2 file3' 'Ip2 file3 file4' 'Ip3 file2 file4 file5 file6'
Text_Array_Parameter=( 'Ip1 file1 file2 file3' 'Ip2 file3 file4' 'Ip3 file2 file4 file5 file6' )
for b in $ {!Text_Array_Parameter[@]}; do echo ${Text_Array_Parameter[$b]} done + Text_Array_Parameter=('Ip1 file1 file2 file3' 'Ip2 file3 file4' 'Ip3 file2 file4 file5 file6') + for b in '${!Text_Array_Parameter[@]}
' + echo Ip1 file1 file2 file3 Ip1 file1 file2 file3 + for b in '$ {!Text_Array_Parameter[@]}' + echo Ip2 file3 file4 Ip2 file3 file4 + for b in '${!Text_Array_Parameter[@]}
' + echo Ip3 file2 file4 file5 file6 Ip3 file2 file4 file5 file6
So there is definitely something going on in the in the shell script where it is loosing something in the process.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubs
[JIRA] [workflow-plugin] (JENKINS-33614) Link to script approval from build console
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-33614 Link to script approval from build console Change By: Patrick Wolf Labels: followup Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [script-security-plugin] (JENKINS-22660) More flexible UI for approved signatures
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-22660 More flexible UI for approved signatures Change By: Patrick Wolf Labels: followup Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [script-security-plugin] (JENKINS-23578) REST/CLI access to ScriptApproval
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-23578 REST/CLI access to ScriptApproval Change By: Patrick Wolf Labels: cli followup rest security Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [google-login-plugin] (JENKINS-32536) Allow for multiple domains
Title: Message Title David Feldsine commented on JENKINS-32536 Re: Allow for multiple domains I would even go for z.com allows @z.com as well as @y.z.com as well as x.y.z.com Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31831) Allow Workflow Snippet Generator to be used outside of a configuration page
Title: Message Title Andrew Melo commented on JENKINS-31831 Re: Allow Workflow Snippet Generator to be used outside of a configuration page I hit the same issue as squalou jenkins. It's nice to have the snippet generator outside of a configuration page, but having it next to the actual configuration box was much more convenient to use. Is there any reason it can't be at both locations? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Daniel Beck commented on JENKINS-28289 Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy Probably best as a separate issue. This one has too much history IMO. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35023) Slave configuration page time-outs
Title: Message Title Daniel Beck resolved as Cannot Reproduce Possible bug or core interaction in Credentials Plugin, upgrading that fixes this. Jenkins / JENKINS-35023 Slave configuration page time-outs Change By: Daniel Beck Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31831) Allow Workflow Snippet Generator to be used outside of a configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31831 Re: Allow Workflow Snippet Generator to be used outside of a configuration page Code changed in jenkins User: Jesse Glick Path: src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/config.jelly src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/config.jelly http://jenkins-ci.org/commit/workflow-cps-plugin/bf459ff0487f86d2e581e2ac15ee6bca5a2c9637 Log: Merge pull request #13 from jglick/Snippetizer-link- JENKINS-31831 JENKINS-31831 Amendment to display a link in the config form Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/7d9e3b2024b9...bf459ff0487f Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31831) Allow Workflow Snippet Generator to be used outside of a configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31831 Re: Allow Workflow Snippet Generator to be used outside of a configuration page Code changed in jenkins User: Jesse Glick Path: src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/config.jelly src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/config.jelly http://jenkins-ci.org/commit/workflow-cps-plugin/c8319cede23d31fc09e467f7b22e7836b273634f Log: JENKINS-31831 Amendment to display a link in the config form, since Jenkins 2 suppresses the sidepanel on configure. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [warnings-plugin] (JENKINS-34157) Warnings plugin doesn't allow environment variables in file names
Title: Message Title Ulli Hafner reopened an issue Jenkins / JENKINS-34157 Warnings plugin doesn't allow environment variables in file names Change By: Ulli Hafner Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [warnings-plugin] (JENKINS-34157) Warnings plugin doesn't allow environment variables in file names
Title: Message Title Ulli Hafner commented on JENKINS-34157 Re: Warnings plugin doesn't allow environment variables in file names Or maybe the problem is the place of the expansion! Where should the environment variable be expanded? On master or slave? (I.e. which node has the correct value?) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [analysis-core-plugin] (JENKINS-30735) Can't use variables in result files path pattern
Title: Message Title Ulli Hafner commented on JENKINS-30735 Re: Can't use variables in result files path pattern Where should the environment variable be expanded? On master or slave? (I.e. which node has the correct value?) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [warnings-plugin] (JENKINS-34157) Warnings plugin doesn't allow environment variables in file names
Title: Message Title
Ulli Hafner resolved as Cannot Reproduce
In my test environment variables are correctly expanded.
How is your environment variable set?
Can you add a build step that echoes the variable?
echo value=${CLEARCASE_VIEWPATH};
Jenkins / JENKINS-34157
Warnings plugin doesn't allow environment variables in file names
Change By:
Ulli Hafner
Status:
Open Resolved
Resolution:
Cannot Reproduce
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails f
[JIRA] [active-choices-plugin] (JENKINS-34188) jenkins.log noise: "script parameter ... is not an instance of Java.util.Map."
Title: Message Title Ben Hines commented on JENKINS-34188 Re: jenkins.log noise: "script parameter ... is not an instance of Java.util.Map." We also have this issue, it's super annoying. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [warnings-plugin] (JENKINS-34157) Warnings plugin doesn't allow environment variables in file names
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34157 Re: Warnings plugin doesn't allow environment variables in file names Code changed in jenkins User: Ulli Hafner Path: src/test/java/plugins/WarningsPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/11b0e681946950461406e9fd4e4bd35211f85347 Log: JENKINS-34157 Added test case that shows that environment variabes are expanded. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [copyartifact-plugin] (JENKINS-34959) Permissions to copy artifact
Title: Message Title ikedam commented on JENKINS-34959 Re: Permissions to copy artifact If you use a multi-configuration project, it might be affected by JENKINS-34758 . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [copyartifact-plugin] (JENKINS-34959) Permissions to copy artifact
Title: Message Title ikedam resolved as Not A Defect It sounds that TRIGGER_JOB_NAME is undefined or empty. If you passed a valid value to TRIGGER_JOB_NAME, the log would be Unable to find project for artifact copy: (the value of TRIGGER_JOB_NAME). Check your configuration or report detailed steps to reproduce the problem. Jenkins / JENKINS-34959 Permissions to copy artifact Change By: ikedam Status: Open Resolved Assignee: ikedam Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [cloudbees-folder-plugin] (JENKINS-35112) Should not be allowed to delete a ComputedFolder in progress
Title: Message Title Jesse Glick commented on JENKINS-35112 Re: Should not be allowed to delete a ComputedFolder in progress Noticed in conjunction with JENKINS-35111. Computation could not be aborted; and if you try to delete the organization folder anyway, things go crazy. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cloudbees-folder-plugin] (JENKINS-35112) Should not be allowed to delete a ComputedFolder in progress
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-35112 Should not be allowed to delete a ComputedFolder in progress Issue Type: Bug Assignee: Unassigned Components: cloudbees-folder-plugin Created: 2016/May/24 9:43 PM Labels: robustness multibranch Priority: Major Reporter: Jesse Glick If a FolderComputation is running: AbstractFolder/tasks-new.jelly should not show the delete link ComputedFolder.performDelete, if called anyway, should try hard to cancel any running computation
[JIRA] [copyartifact-plugin] (JENKINS-35103) BUILD_SELECTOR is not passed to matrix subprojects
Title: Message Title ikedam resolved as Duplicate Sounds the issue reported in JENKINS-34758 . matrix-project 1.7 fixed the issue. Please try that. Jenkins / JENKINS-35103 BUILD_SELECTOR is not passed to matrix subprojects Change By: ikedam Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-26578) Adjuncts do not include CSS correctly for removable dom fragments
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26578 Re: Adjuncts do not include CSS correctly for removable dom fragments Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsSelectHelper.java src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/DomainWrapper/newCredentials.jelly src/main/resources/lib/credentials/select.jelly src/main/resources/lib/credentials/select/select.js http://jenkins-ci.org/commit/credentials-plugin/cbb9fda8fb897ca40ec1520342c5ca86bb5bf97f Log: JENKINS-26578 More refined workaround Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [external-workspace-manager-plugin] (JENKINS-35110) [EWM] Support global/node exws configs
Title: Message Title Alexandru Somai started work on JENKINS-35110 Change By: Alexandru Somai Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [java-client-api] (JENKINS-35108) Upgrade Maven Plugins
Title: Message Title Karl-Heinz Marbaise closed an issue as Fixed Done in cd859c72f14e5c3031e677e78844133c941df89d Jenkins / JENKINS-35108 Upgrade Maven Plugins Change By: Karl-Heinz Marbaise Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [credentials-plugin] (JENKINS-35109) Unable To Create / Modify Nodes After Updating to Credentials Plugin 2.0.1
Title: Message Title Nicholas Raymond resolved as Duplicate Jenkins / JENKINS-35109 Unable To Create / Modify Nodes After Updating to Credentials Plugin 2.0.1 Change By: Nicholas Raymond Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [credentials-plugin] (JENKINS-35109) Unable To Create / Modify Nodes After Updating to Credentials Plugin 2.0.1
Title: Message Title Nicholas Raymond commented on JENKINS-35109 Re: Unable To Create / Modify Nodes After Updating to Credentials Plugin 2.0.1 Just saw this was already reported and fixed in JENKINS-35075 . Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gerrit-trigger-plugin] (JENKINS-35092) No gerrit variables when using gerrit trigger
Title: Message Title Darren Maki commented on JENKINS-35092 Re: No gerrit variables when using gerrit trigger This may be of use to you: https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [credentials-plugin] (JENKINS-35109) Unable To Create / Modify Nodes After Updating to Credentials Plugin 2.0.1
Title: Message Title Nicholas Raymond updated an issue Jenkins / JENKINS-35109 Unable To Create / Modify Nodes After Updating to Credentials Plugin 2.0.1 Change By: Nicholas Raymond After updating to Credentials Plugin 2.0.1 (Currently using 1.28), we are unable to create a new Dumb Slave / Permanent Agent and we're also unable to modify any existing agents. The only node that can be successfully modified is 'master'.h4. Steps to Replicate* Install Credentials Plugin 1.28* Update plugin to 2.0.1 and restart the Jenkins service* Once Jenkins is back online, http:///computer/new* Provide a name and choose "Dumb Slave" (Jenkins 1.x) or "Permanent Agent" (Jenkins 2.x), press OK* The page will sit in a loading state and never return the next screen.Additionally, the same result will occur if you find a node and choose "Configure" for it.h4. Workaround* Downgrading the plugin back to 1.28 and restarting the Jenkins service resolved the issue.This was tested on both Jenkins 1.650 and 2.6. I could not locate any errors or messages being reported to jenkins.log around this behaviour Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [credentials-plugin] (JENKINS-35109) Unable To Create / Modify Nodes After Updating to Credentials Plugin 2.0.1
Title: Message Title Nicholas Raymond updated an issue Jenkins / JENKINS-35109 Unable To Create / Modify Nodes After Updating to Credentials Plugin 2.0.1 Change By: Nicholas Raymond After updating to Credentials Plugin 2.0.1 (Currently using 1.28), we are unable to create a new Dumb Slave / Permanent Agent and we're also unable to modify any existing agents. The only node that can be successfully modified is 'master'.h4. Steps to Replicate* Install Credentials Plugin 1.28* Update plugin to 2.0.1 and restart the Jenkins service* Once Jenkins is back online, http:///computer/new* Provide a name and choose "Dumb Slave" (Jenkins 1.x) or "Permanent Agent" (Jenkins 2.x), press OK* The page will sit in a loading state and never return the next screen.Additionally, the same result will occur if you find a node and choose "Configure" for it.h4. Workaround* Downgrading the plugin back to 1.28 and restarting the Jenkins service resolved the issue.This was tested on both Jenkins 1.650 and 2.6. I could not locate any errors or messages being reported to jenkins.log around this behaviour behavior . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [credentials-plugin] (JENKINS-35109) Unable To Create / Modify Nodes After Updating to Credentials Plugin 2.0.1
Title: Message Title Nicholas Raymond created an issue Jenkins / JENKINS-35109 Unable To Create / Modify Nodes After Updating to Credentials Plugin 2.0.1 Issue Type: Bug Assignee: stephenconnolly Components: credentials-plugin Created: 2016/May/24 8:53 PM Priority: Critical Reporter: Nicholas Raymond After updating to Credentials Plugin 2.0.1 (Currently using 1.28), we are unable to create a new Dumb Slave / Permanent Agent and we're also unable to modify any existing agents. The only node that can be successfully modified is 'master'. Steps to Replicate Install Credentials Plugin 1.28 Update plugin to 2.0.1 and restart the Jenkins service Once Jenkins is back online, http:///computer/new Provide a name and choose "Dumb Slave" (Jenkins 1.x) or "Permanent Agent" (Jenkins 2.x), press OK The page will sit in a loading state and never return the next screen.
[JIRA] [java-client-api] (JENKINS-35108) Upgrade Maven Plugins
Title: Message Title Karl-Heinz Marbaise created an issue Jenkins / JENKINS-35108 Upgrade Maven Plugins Issue Type: Improvement Assignee: Karl-Heinz Marbaise Components: java-client-api Created: 2016/May/24 8:46 PM Priority: Minor Reporter: Karl-Heinz Marbaise maven-clean-plugin to 3.0.0 maven-jar-plugin to 3.0.0 maven-resources-plugin to 3.0.0 Add Comment
[JIRA] [workflow-plugin] (JENKINS-33925) Test framework for Jenkinsfile
Title: Message Title Jesse Glick commented on JENKINS-33925 Re: Test framework for Jenkinsfile a job type that was basically identical to the existing Pipeline job type (with both inline and from-SCM options) that would run the Pipeline script in the test environment Hmm, this would be something very different from the JenkinsRule proposal. I do not think this kind of setup would fly. It would be fine for interactive testing but it would not work well for automated testing. […] steps that depend on generated output from previous steps that we may have mocked out/overridden Perhaps the mocking facility could be used in the JenkinsRule scenario, as a kind of hybrid approach. So you could declare that, for example, all mail steps, or the third node step, or any sh step taking the script argument mvn clean test, etc., should print the following output, or return the following result object, or fail with the following error message. Unmentioned steps would run “for real” by default, or you could declare that by default these would fail the test, but you could explicitly ask for some to follow the real behavior. Some of these facilities would actually be useful in Pipeline plugin tests, too, which would help validate the concept and iron out bugs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ec2-plugin] (JENKINS-35107) ec2 plugin documentation states that Windows is unsupported, is it?
Title: Message Title J C created an issue Jenkins / JENKINS-35107 ec2 plugin documentation states that Windows is unsupported, is it? Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/May/24 8:05 PM Priority: Minor Reporter: J C In the documentation at: https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin It states that "Windows is currently unsupported." However, none of the runtime help information when actually using the windows support indicates that windows is unsupported. Is windows supported or unsupported? Add Comment
[JIRA] [workflow-plugin] (JENKINS-34596) Set visible flag when Jenkinsfile is taken from a trusted revision rather than PR head
Title: Message Title Jesse Glick started work on JENKINS-34596 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [hp-application-automation-tools-plugin] (JENKINS-35106) HP ALM plugin fails to find junit results file
Title: Message Title mpendas created an issue Jenkins / JENKINS-35106 HP ALM plugin fails to find junit results file Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2016/May/24 7:52 PM Environment: Jenkins ver. 1.642 HP Application Automation Tools plugin ver. 4.01 java version "1.7.0_71" OpenJDK Runtime Environment (rhel-2.5.3.1.el6-x86_64 u71-b14) OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) Red Hat Enterprise Linux Server release 6.6 (Santiago) Priority: Minor Reporter: mpendas I am only trying to upload test results to ALM. This is running on RedHat Linux. No HP LAM software is installed on the jenkins machine. The Junit plugin finds the results file the HP ALM plugin does not find the file: Recording test results Build step 'Publish JUnit test result report' changed build result to UNSTABLE INFO: 'Upload test result to ALM' Post Build Step is being invoked. INFO: No Test Report found. INFO: 'Upload test result to ALM' Completed. Finished: UNSTABLE The file path for both plugins is: **/fit_tests/ApiResults.xml
[JIRA] [workflow-plugin] (JENKINS-34596) Set visible flag when Jenkinsfile is taken from a trusted revision rather than PR head
Title: Message Title Antonio Muñiz commented on JENKINS-34596 Re: Set visible flag when Jenkinsfile is taken from a trusted revision rather than PR head introduce a readTrusted step which would work without a checkout How is that going to work with GitSCMSource? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35105) Issue with git credentials InvalidObjectIdException
Title: Message Title Rishi Pampati created an issue Jenkins / JENKINS-35105 Issue with git credentials InvalidObjectIdException Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/May/24 7:23 PM Environment: Jenkins version 2.6 on Windows OS Priority: Blocker Reporter: Rishi Pampati javax.servlet.ServletException: org.eclipse.jgit.errors.InvalidObjectIdException: Invalid id : C:\Windows\TEMP\hudson8725852661617820 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) 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.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) 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.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.Servle
[JIRA] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title
Etienne Bec edited a comment on JENKINS-28289
Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
I will give you some background. Our network is behind a corporate proxy and thus we need to go through it to access to Internet. That's why we have defined the two standard environment variables, {{http_proxy}} and {{no_proxy}}, to configure several tools (curl for instance), to use the proxy. The slaves and the master are on the same network so they can communicate directly, that's why we didn't set the system properties {{http.proxyHost}} and so on. :) We were previously running Jenkins 1.596.3 which uses remoting 2.47, and this version doesn't include the PR27. And with this PR the trouble begins because the slave started to take in account only the first env var I mentioned: {{http_proxy}}. {{no_proxy}} is +never+ read. And the PR55 which is related to this issue doesn't fix this either. It just introduced the use of {{ProxySelector}} which automatically take in account the exception list ... defined by the system property {{http.nonProxyHosts}}. And as in the PR27 it reads the {{http_proxy}} env var as a fallback, but doesn't use {{no_proxy}} at all! :( To be more clear, we +don't use+ the proxy features on our side. It's just that the slave started with the PR27 to read some env var it should not (because that's not how the JVM should be configured). So either we need to take in account {{no_proxy}} or we remove from the two methods the part which use {{http_proxy}}: https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/Util.java#L114 & https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/Util.java#L114.I've reopened this issue because to my understanding the goal of this issue wasn't just to add the support for {{http.nonProxyHosts}} but to correct PR27. Should we create a new issue?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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.
[JIRA] [git-client-plugin] (JENKINS-35104) git plugin still checks out all branches when refspec set
Title: Message Title Allon Bendavid created an issue Jenkins / JENKINS-35104 git plugin still checks out all branches when refspec set Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin, git-plugin Created: 2016/May/24 7:13 PM Priority: Blocker Reporter: Allon Bendavid We are getting a lot of these errors: ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from git@gitlab:xxx/main.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:810) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1066) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1097) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:136) at hudson.model.Run.execute(Run.java:1738) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: hudson.plugins.git.GitException: Command "/home/cruise/tools/hudson.plugins.git.GitTool/git-2.7.1/git -c core.askpass=true fetch --no-tags --progress g...@gitlab.xxx.com:xxx/main.git +refs/heads/master:refs/remotes/origin/master" returned status code 128: stdout: stderr: error: refs/remotes/origin/ does not point to a valid object! . fatal: pack has 120 u
[JIRA] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title
Etienne Bec edited a comment on JENKINS-28289
Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
I will give you some background. Our network is behind a corporate proxy and thus we need to go through it to access to Internet. That's why we have defined the two standard environment variables, {{http_proxy}} and {{no_proxy}}, to configure several tools (curl for instance), to use the proxy. The slaves and the master are on the same network so they can communicate directly, that's why we didn't set the system properties {{http.proxyHost}} and so on.We were previously running Jenkins 1.596.3 which uses remoting 2.47, and this version doesn't include the PR27. And with this PR the trouble begins because the slave started to take in account only the first env var I mentioned: {{http_proxy}}. {{no_proxy}} is +never+ read. And the PR55 which is related to this issue doesn't fix this either. It just introduced the use of {{ProxySelector}} which automatically take in account the exception list ... defined by the system property {{http.nonProxyHosts}}. And as in the PR27 it reads the {{ http_proxy }} env var as a fallback, but doesn't use {{no_proxy}} at all!To be more clear, we +don't use+ the proxy features on our side. It's just that the slave started with the PR27 to read some env var it should not (because that's not how the JVM should be configured). So either we need to take in account {{no_proxy}} or we remove from the two methods the part which use {{ http_proxy }} : https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/Util.java#L114 & https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/Util.java#L114.I've reopened this issue because to my understanding the goal of this issue wasn't just to add the support for {{http.nonProxyHosts}} but to correct PR27. Should we create a new issue?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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.
[JIRA] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Etienne Bec commented on JENKINS-28289 Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy I will give you some background. Our network is behind a corporate proxy and thus we need to go through it to access to Internet. That's why we have defined the two standard environment variables, http_proxy and no_proxy, to configure several tools (curl for instance), to use the proxy. The slaves and the master are on the same network so they can communicate directly, that's why we didn't set the system properties http.proxyHost and so on. We were previously running Jenkins 1.596.3 which uses remoting 2.47, and this version doesn't include the PR27. And with this PR the trouble begins because the slave started to take in account only the first env var I mentioned: http_proxy. no_proxy is never read. And the PR55 which is related to this issue doesn't fix this either. It just introduced the use of ProxySelector which automatically take in account the exception list ... defined by the system property http.nonProxyHosts. And as in the PR27 it reads the http_proxy env var as a fallback, but doesn't use no_proxy at all! To be more clear, we don't use the proxy features on our side. It's just that the slave started with the PR27 to read some env var it should not (because that's not how the JVM should be configured). So either we need to take in account no_proxy or we remove from the two methods the part which use http_proxy: https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/Util.java#L114 & https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/Util.java#L114. I've reopened this issue because to my understanding the goal of this issue wasn't just to add the support for http.nonProxyHosts but to correct PR27. Should we create a new issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-34596) Set visible flag when Jenkinsfile is taken from a trusted revision rather than PR head
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-34596 Set visible flag when Jenkinsfile is taken from a trusted revision rather than PR head Change By: Jesse Glick Labels: multibranch Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitbucket-branch-source-plugin] (JENKINS-33701) Add SCM Repository browser support to Multi-branch project
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33701 Add SCM Repository browser support to Multi-branch project Using bitbucket-branch-source? Or what? Change By: Jesse Glick Component/s: bitbucket-branch-source-plugin Component/s: git-plugin Component/s: scm-api-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-branch-source-plugin] (JENKINS-34548) InjectedTest failure: github plugin fails to start
Title: Message Title Jesse Glick resolved as Cannot Reproduce Whatever the original error was, it would need to be diagnosed before it is useful to file an issue. Jenkins / JENKINS-34548 InjectedTest failure: github plugin fails to start Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-branch-source-plugin] (JENKINS-34966) GH branch source uses wrong commit
Title: Message Title Jesse Glick resolved as Duplicate Most likely related to JENKINS-33237 if not an exact duplicate. Jenkins / JENKINS-34966 GH branch source uses wrong commit Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-branch-source-plugin] (JENKINS-34966) GH branch source uses wrong commit
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-34966 GH branch source uses wrong commit Change By: Jesse Glick This looks similar to, but distinct from # JENKINS- 34727. Somehow the branch source plugin gets confused about what is the "most recent" commit for a PR, and falls over trying to check out the branch, even if I repeatedly hit the "branch indexing" button.The confusing thing is that I'm not sure how the checkout is failing. My instance is at http://jenkins.accre.vanderbilt.edu/job/LStore-Branches/branch/PR-85/, but to put the text here, this is the order of events I observed1) Commit/push 120ff4dbc33db1b410bbbcc681f4fd53c125c1e1 to GH which shows up as 808a15263d77d8166bda573509d58e44a9f1b2b7 in the merge commit2) Jenkins is notified via webhook, who then performs build #233) Commit bb5f59a71d0221d4f3d0f9c61f7733275a2c8e92 to GH4) Jenkins is notified via webhook, who then performs build #24 with the same commit as before, with a "no changes" message if I drill down into the build. That build bombs with:hudson.plugins.git.GitException: Could not checkout 808a15263d77d8166bda573509d58e44a9f1b2b7 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1992) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:152) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:332) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at hudson.remoting.Engine$1$1.run(Engine.java:85) at java.lang.Thread.run(Thread.java:745) at ..remote call to headnode(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.UserResponse.retrieve(UserRequest.java:252) at hudson.remoting.Channel.call(Channel.java:781) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) at sun.reflect.GeneratedMethodAccessor589.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)5) Manually reindexing and forcing the build doesn't clean up the state.It appears that jenkins is trying to use the old merge commit for some reason, but (as of me typing this), if I manually take the commit SHA1 and type it into the web interface, it gives a commit back. Not that it matters, having the results be stale is also not great.Lemme know if there's more information that I can give.
[JIRA] [copyartifact-plugin] (JENKINS-35103) BUILD_SELECTOR is not passed to matrix subprojects
Title: Message Title
Phillip Kuhrt updated an issue
Jenkins / JENKINS-35103
BUILD_SELECTOR is not passed to matrix subprojects
Change By:
Phillip Kuhrt
A parameter of the type "Build selector for Copy Artifact" works fine when using it in an freestyle job, it copies the artifacts and the windows script {code}echo "%BUILD_SELECTOR%"{code}prints as expected:{code}00:00:00.059 [IntegrationTest] $ cmd /c call C:\Users\JENKIN~1\AppData\Local\Temp\hudson**.bat00:00:00.095 00:00:00.095 C:\Jenkins\workspace\**>echo " true UseNewest true" 00:00:00.095 " true UseNewest true"00:00:00.095 00:00:00.095 C:\Jenkins\workspace\**>exit 0 00:00:00.107 Setting MSBUILD_12_HOME=C:\Program Files (x86)\MSBuild\12.0\Bin\00:00:09.371 Copied 603 artifacts from "**" build number 10{code}When using the same setup (Build selector parameter; windows batch script and copy artifact step) in an matrix job, we get the following result:{code}00:00:00.053 [**] $ cmd /c call C:\Users\JENKIN~1\AppData\Local\Temp\hudson**.bat00:00:00.096 00:00:00.096 C:\Jenkins\workspace\**>echo "" 00:00:00.096 ""00:00:00.097 00:00:00.097 C:\Jenkins\workspace\**>exit 0 00:00:00.110 Setting MSBUILD_12_HOME=C:\Program Files (x86)\MSBuild\12.0\Bin\00:00:00.112 ERROR: Unable to find a build for artifact copy from: Build2/BuildConfiguration=Debug,Slave=**{code}It looks as if the parameter is not passed to the subproject created automatically for each combination. Specifying When specifying the Build selector directly (without variable, choosing "Upstream build that triggered this job" instead of "Specified by build selector"), the artifacts are copied.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [copyartifact-plugin] (JENKINS-35103) BUILD_SELECTOR is not passed to matrix subprojects
Title: Message Title
Phillip Kuhrt updated an issue
Jenkins / JENKINS-35103
BUILD_SELECTOR is not passed to matrix subprojects
Change By:
Phillip Kuhrt
Environment:
Jenkins: 2.5 {code}java.class.path /usr/share/jenkins/jenkins.warjava.class.version 52.0os.name , Linux os.version 3.16.0-4-amd64java.runtime.name x64, Java (TM) SE Runtime Environmentjava.runtime.version 1.8.0_91 -b14java.specification.name Java Platform API Specificationjava.specification.vendor Oracle Corporationjava.specification.version 1.8java.vendor Oracle Corporationjava.vendor.url http://java.oracle.com/java.vendor.url.bug http://bugreport.sun.com/bugreport/java.version 1.8.0_91java.vm.info mixed modejava.vm.name Java HotSpot(TM) 64-Bit Server VMjava.vm.specification.name Java Virtual Machine Specificationjava.vm.specification.vendor Oracle Corporationjava.vm.specification.version 1.8java.vm.vendor Oracle Corporationjava.vm.version 25.91-b14 , matrix-project 1.6 true false , copyartifact 1.38 true false{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [github-branch-source-plugin] (JENKINS-34938) Access commit SHA of webhook payload in Jenkinsfile
Title: Message Title Jesse Glick assigned an issue to Unassigned This would require significant changes to branch indexing in branch-api. BranchNameContributor is irrelevant here. Anyway what is the actual problem you are trying to solve here? With no context I am inclined to reject this. Jenkins / JENKINS-34938 Access commit SHA of webhook payload in Jenkinsfile Change By: Jesse Glick Component/s: github-organization-folder-plugin Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [copyartifact-plugin] (JENKINS-35103) BUILD_SELECTOR is not passed to matrix subprojects
Title: Message Title
Phillip Kuhrt updated an issue
Jenkins / JENKINS-35103
BUILD_SELECTOR is not passed to matrix subprojects
Change By:
Phillip Kuhrt
A parameter of the type "Build selector for Copy Artifact" works fine when using it in an freestyle job, it copies the artifacts and the windows script {code}echo "%BUILD_SELECTOR%"{code}prints as expected:{code}00:00:00.059 [IntegrationTest] $ cmd /c call C:\Users\JENKIN~1\AppData\Local\Temp\hudson**.bat00:00:00.095 00:00:00.095 C:\Jenkins\workspace\**>echo " true UseNewest true" 00:00:00.095 " true UseNewest true"00:00:00.095 00:00:00.095 C:\Jenkins\workspace\**>exit 0 00:00:00.107 Setting MSBUILD_12_HOME=C:\Program Files (x86)\MSBuild\12.0\Bin\00:00:09.371 Copied 603 artifacts from "**" build number 10{code}When using the same setup in an matrix job (Build selector parameter; windows batch script and copy artifact step) in an matrix job , we get the following result:{code}00:00:00.053 [**] $ cmd /c call C:\Users\JENKIN~1\AppData\Local\Temp\hudson**.bat00:00:00.096 00:00:00.096 C:\Jenkins\workspace\**>echo "" 00:00:00.096 ""00:00:00.097 00:00:00.097 C:\Jenkins\workspace\**>exit 0 00:00:00.110 Setting MSBUILD_12_HOME=C:\Program Files (x86)\MSBuild\12.0\Bin\00:00:00.112 ERROR: Unable to find a build for artifact copy from: Build2/BuildConfiguration=Debug,Slave=**{code}It looks as if the parameter is not passed to the subproject created automatically for each combination. Specifying the Build selector directly (without variable, choosing "Upstream build that triggered this job" instead of "Specified by build selector"), the artifacts are copied.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [copyartifact-plugin] (JENKINS-35103) BUILD_SELECTOR is not passed to matrix subprojects
Title: Message Title
Phillip Kuhrt created an issue
Jenkins / JENKINS-35103
BUILD_SELECTOR is not passed to matrix subprojects
Issue Type:
Bug
Assignee:
Unassigned
Components:
copyartifact-plugin
Created:
2016/May/24 6:42 PM
Environment:
Jenkins: 2.5 {code} java.class.path /usr/share/jenkins/jenkins.war java.class.version 52.0 os.name Linux os.version 3.16.0-4-amd64 java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.8.0_91-b14 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_91 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.91-b14 matrix-project 1.6 true false copyartifact 1.38 true false {code}
Labels:
plugin
Priority:
Major
Reporter:
Phillip Kuhrt
[JIRA] [copyartifact-plugin] (JENKINS-9622) Add build selector to parameterized trigger
Title: Message Title Phillip Kuhrt commented on JENKINS-9622 Re: Add build selector to parameterized trigger This looks like a text parameter when you print it from a command line or view it in a parameter analysis plugin (Simple Parameterized Builds Report, "Rebuild Last", etc.); you might be able to pass something like this as a workaround: "copyartifact@1.38"> true UseNewest true Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [warnings-plugin] (JENKINS-35100) Warnings Compiler Plugin for Visual Studio c++
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-35100 Warnings Compiler Plugin for Visual Studio c++ Change By: Ulli Hafner Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [warnings-plugin] (JENKINS-35100) Warnings Compiler Plugin for Visual Studio c++
Title: Message Title Ulli Hafner commented on JENKINS-35100 Re: Warnings Compiler Plugin for Visual Studio c++ Did you try MS Build parser? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jobconfighistory-plugin] (JENKINS-30089) new config history created on each multibranch build
Title: Message Title Jesse Glick assigned an issue to Stefan Brausch We need an API by which one plugin (branch-api) can tell another (jobConfigHistory) that a given Item is generated and configuration changes are thus not interesting. Anyway in this case jobConfigHistory can just be configured to ignore updates which do not actually change config.xml. I am surprised it does not do so by default. Jenkins / JENKINS-30089 new config history created on each multibranch build Change By: Jesse Glick Component/s: multi-branch-project-plugin Labels: api multibranch Assignee: Matthew DeTullio Stefan Brausch Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [pipeline-utility-steps-plugin] (JENKINS-35036) Unable to pass map of closures and failFast parameter to "parallel" pipeline step
Title: Message Title Jesse Glick resolved as Not A Defect See answer. Jenkins / JENKINS-35036 Unable to pass map of closures and failFast parameter to "parallel" pipeline step Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cloudbees-folder-plugin] (JENKINS-33622) Classic job configuration page shown for Multibranch projects
Title: Message Title Jesse Glick commented on JENKINS-33622 Re: Classic job configuration page shown for Multibranch projects If fixing, check https://github.com/jenkinsci/workflow-cps-plugin/pull/13. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cli] (JENKINS-34986) Dockerized Jenkins cannot create jobs in CloudBees Folders from outside of the container [HTTP 400]
Title: Message Title Jesse Glick resolved as Not A Defect Almost certainly either a bug in JJB, or a user error. Jenkins / JENKINS-34986 Dockerized Jenkins cannot create jobs in CloudBees Folders from outside of the container [HTTP 400] Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cloudbees-folder-plugin] (JENKINS-33762) Per-folder tool installations
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33762 Per-folder tool installations Change By: Jesse Glick Summary: Configure JDK at Per- folder level tool installations Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [publish-over-ssh-plugin] (JENKINS-33764) Configure SSH credentials at folder level
Title: Message Title Jesse Glick assigned an issue to bap So probably just means that this plugin needs to be integrated with credentials. Jenkins / JENKINS-33764 Configure SSH credentials at folder level Change By: Jesse Glick Component/s: publish-over-ssh-plugin Component/s: cloudbees-folder-plugin Assignee: Owen Wood bap Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/opto
[JIRA] [core] (JENKINS-35023) Slave configuration page time-outs
Title: Message Title Alexey Bychko commented on JENKINS-35023 Re: Slave configuration page time-outs yes, it does Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitbucket-branch-source-plugin] (JENKINS-33865) Double Build on Multibranch Pipeline with open PR
Title: Message Title Jesse Glick assigned an issue to Antonio Muñiz Jenkins / JENKINS-33865 Double Build on Multibranch Pipeline with open PR Change By: Jesse Glick Component/s: bitbucket-branch-source-plugin Component/s: workflow-plugin Labels: multibranch Assignee: Jesse Glick Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitbucket-branch-source-plugin] (JENKINS-33865) Double Build on Multibranch Pipeline with open PR
Title: Message Title Jesse Glick commented on JENKINS-33865 Re: Double Build on Multibranch Pipeline with open PR github-branch-source automatically skips PRs filed from origin branches. I do not know enough about BitBucket to be sure that this is making the analogous request. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35023) Slave configuration page time-outs
Title: Message Title Daniel Beck commented on JENKINS-35023 Re: Slave configuration page time-outs According to JENKINS-35050 an update of the Credentials Plugin resolves this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Daniel Beck commented on JENKINS-28289 Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy Etienne Bec To clarify, this issue is fixed as described, but you're using yet another environment variable, and that one isn't used? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35087) Old data not upgrading from 1.653 to 1.651.2
Title: Message Title Daniel Beck commented on JENKINS-35087 Re: Old data not upgrading from 1.653 to 1.651.2 but isn't more logical to have releases get a higher number? or is it normal to go from a higher release number to a lower one? This code is part of a bug fix that was introduced in 1.653 and was backported to 1.651.2. When backporting, the version shown on the UI wasn't adapted. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
