[JIRA] (JENKINS-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis
Title: Message Title Yafim Kazak commented on JENKINS-39332 Re: ApiSlRuntimeErrors.UnsafeCode error during analysis Hi, Please post the following so we can work on reproducing and tracing the issue: Jenkins configuration files - build.xml, Log, Config.xml - all obtainable from Jenkins folder on master- for example: C:\Jenkins\jjobs\\config.xml, c:\Jenkins\jobs\\builds\\log,build.xml. LR version Did you set your controller settings differently than default? i.e. change result options or any others when you changed LR host? From first impression it seems as if something has changed in your Analysis settings and default HTML report template that is used to create the HTML report published to Jenkins doesn't exist. Have you customized analysis settings in some way that might affect reports on this LR host? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-39332 ApiSlRuntimeErrors.UnsafeCode error during analysis Change By: Yafim Kazak Labels: jenkins plugin plugins LoadRunner LrAnalysisLauncher slave windows Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis
Title: Message Title Yafim Kazak started work on JENKINS-39332 Change By: Yafim Kazak Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis
Title: Message Title Yafim Kazak assigned an issue to Yafim Kazak Jenkins / JENKINS-39332 ApiSlRuntimeErrors.UnsafeCode error during analysis Change By: Yafim Kazak Assignee: Ofir Shaked Yafim Kazak Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39116) JDK auto installation doesn't start
Title: Message Title Fukusuke Takahashi edited a comment on JENKINS-39116 Re: JDK auto installation doesn't start bq. Make sure you're not e.g. limiting on which nodes the zip installer works with a label _expression_ or something.After removing the label, JDK installtion work installation worked correctly.(I did'nt know the label effect)I’m sorry for taking up your time. Thank you for your corporation advice . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39116) JDK auto installation doesn't start
Title: Message Title Fukusuke Takahashi edited a comment on JENKINS-39116 Re: JDK auto installation doesn't start Thank you for reply.I added build step(Invoke Gradle script) but JDK auto installation wouldn't start.Although JDK auto installation didn't start, Gradle (also 's, as well as Ant ) instalaltion seemed to work 's, installation worked correctly.Is threre anything else to check ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39116) JDK auto installation doesn't start
Title: Message Title Fukusuke Takahashi edited a comment on JENKINS-39116 Re: JDK auto installation doesn't start Thank you for reply.I added build step(Invoke Gradle script) but JDK auto installation wouldn't start.Although JDK auto installation doesn didn 't start, Gradle instalaltion work correctly. (also Ant) instalaltion seemed to work correctly. Is threre anything else to check ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39116) JDK auto installation doesn't start
Title: Message Title Fukusuke Takahashi edited a comment on JENKINS-39116 Re: JDK auto installation doesn't start Thank you for reply.I added build step(Invoke Gradle script) but JDK auto installation never wouldn't start.Although JDK auto installation doesn't start, Gradle instalaltion work correctly.(also Ant)Is threre anything else to check ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39116) JDK auto installation doesn't start
Title: Message Title Fukusuke Takahashi updated an issue Jenkins / JENKINS-39116 JDK auto installation doesn't start Change By: Fukusuke Takahashi A DESCRIPTION OF THE PROBLEM : JDK auto installation doesn't start.STEPS TO FOLLOW TO REPRODUCE THE PROBLEM : 1. Install Jenkins 2.19.1.2. Set up Global Tool Configuration. Create two JDK auto installation setting as follows. Jenkins -> Global Tool Configuration -> JDK -> JDK installations - install automatically ON - Add Installer - Extract *.zip/*.tar.gz3. Create new job. Jenkins -> New Item -> Freestyle project -> TESTPROJECT -> OK - General tab - JDK : select above jdk auto installer from select box.4. Build Now 5. Check console output from build history.Actual Results 6. JDK auto installation doesn't starts.Expected Results6. JDK auto installation normally starts. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-39116) JDK auto installation doesn't start
Title: Message Title Fukusuke Takahashi updated an issue Jenkins / JENKINS-39116 JDK auto installation doesn't start Change By: Fukusuke Takahashi A DESCRIPTION OF THE PROBLEM : JDK auto installation doesn't start.STEPS TO FOLLOW TO REPRODUCE THE PROBLEM : 1. Install Jenkins 2.19.1.2. Set up Global Tool Configuration. Create two JDK auto installation setting as follows. Jenkins -> Global Tool Configuration -> JDK -> JDK installations - install automatically ON - Add Installer - Extract *.zip/*.tar.gz3. Create new job. Jenkins -> New Item -> Freestyle project -> TESTPROJECT -> OK - General tab - JDK : select above jdk auto installer from select box.4. Build Now 5. Check console output from build history.Actual Results 6. JDK auto installation doesn't start starts .Expected Results6. JDK auto installation start starts . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-39116) JDK auto installation doesn't start
Title: Message Title Fukusuke Takahashi updated an issue Jenkins / JENKINS-39116 JDK auto installation doesn't start Change By: Fukusuke Takahashi A DESCRIPTION OF THE PROBLEM : JDK auto installation doesn't start.STEPS TO FOLLOW TO REPRODUCE THE PROBLEM : 1. Install Jenkins 2.19.1.2. Set up Global Tool Configuration. Create two JDK auto installation setting as follows. Jenkins -> Global Tool Configuration -> JDK -> JDK installations - install automatically ON - Add Installer - Extract *.zip/*.tar.gz3. Create new job. Jenkins -> New Item -> Freestyle project -> TESTPROJECT -> OK - General tab - JDK : select above jdk auto installer from select box.4. Build Now 5. Check console output from build history.Actual Results 6. JDK installation doesn't occur start .Expected Results6. JDK installation occur start . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-39116) JDK auto installation doesn't start
Title: Message Title Fukusuke Takahashi edited a comment on JENKINS-39116 Re: JDK auto installation doesn't start Than you for reply.I added build step(Invoke Gradle script) but JDK auto installation never occur start .Although JDK auto installation doesn't occer start , Gradle instalaltion work correctly.(also Ant)Is threre anything else to check ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39116) JDK auto installation doesn't start
Title: Message Title Fukusuke Takahashi updated an issue Jenkins / JENKINS-39116 JDK auto installation doesn't start Change By: Fukusuke Takahashi A DESCRIPTION OF THE PROBLEM : JDK auto installation doesn't occur start .STEPS TO FOLLOW TO REPRODUCE THE PROBLEM : 1. Install Jenkins 2.19.1.2. Set up Global Tool Configuration. Create two JDK auto installation setting as follows. Jenkins -> Global Tool Configuration -> JDK -> JDK installations - install automatically ON - Add Installer - Extract *.zip/*.tar.gz3. Create new job. Jenkins -> New Item -> Freestyle project -> TESTPROJECT -> OK - General tab - JDK : select above jdk auto installer from select box.4. Build Now 5. Check console output from build history.Actual Results 6. JDK installation doesn't occur.Expected Results6. JDK installation occur. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-39116) JDK auto installation doesn't start
Title: Message Title Fukusuke Takahashi edited a comment on JENKINS-39116 Re: JDK auto installation doesn't start Than Thank you for reply.I added build step(Invoke Gradle script) but JDK auto installation never start.Although JDK auto installation doesn't start, Gradle instalaltion work correctly.(also Ant)Is threre anything else to check ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39116) JDK auto installation doesn't start
Title: Message Title Fukusuke Takahashi updated an issue Jenkins / JENKINS-39116 JDK auto installation doesn't start Change By: Fukusuke Takahashi Summary: JDK auto installation doesn't occur start Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39116) JDK auto installation doesn't occur
Title: Message Title Fukusuke Takahashi edited a comment on JENKINS-39116 Re: JDK auto installation doesn't occur Than you for reply.I added build step(Invoke Gradle script) but JDK auto installation never occer occur .Although JDK auto installation doesn't occer, Gradle instalaltion work correctly.(also Ant)Is threre anything else to check ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39362) Build test classpath is inconsistent: mockito-all clashes with hamcrest-core
Title: Message Title Frédéric Chuong created an issue Jenkins / JENKINS-39362 Build test classpath is inconsistent: mockito-all clashes with hamcrest-core Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2016/Oct/29 2:35 AM Environment: promoted-builds-plugin f7589c3c3e76f357393c6431a6412f2bc1e55ee7 Labels: dependencies junit Priority: Minor Reporter: Frédéric Chuong Trying to implement semantically improved unit test results in a runtime error: mvn test -Dtest=MatcherTest -Dconcurrency=1 -DtrimStackTrace=false --- Test set: hudson.plugins.promoted_builds.MatcherTest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.068 sec <<< FAILURE! - in hudson.plugins.promoted_builds.MatcherTest test(hudson.plugins.promoted_builds.MatcherTest) Time elapsed: 0.008 sec <<< ERROR! java.lang.NoSuchMethodError: org.hamcrest.Matcher.describeMismatch(Ljava/lang/Object;Lorg/hamcrest/Description;)V
[JIRA] (JENKINS-39264) 17:50:28 ERROR: Error fetching remote repo 'origin'
Title: Message Title Mark Waite closed an issue as Not A Defect Please use the Jenkins users mailing list to ask configuration and authentication questions. There are many more people on the mailing list willing to answer questions than there are developers working on the git plugin. Jenkins / JENKINS-39264 17:50:28 ERROR: Error fetching remote repo 'origin' Change By: Mark Waite Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-37978) Reveal changed paths in git commits to conditions in pipeline
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-37978 Reveal changed paths in git commits to conditions in pipeline Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39250) Add option to disable automatic user creation in Git plugin
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-39250 Add option to disable automatic user creation in Git plugin Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39221) Pipeline Job seems to ignore Branch Specifiers in config.xml when being triggered by BitBucket Plugin
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-39221 Pipeline Job seems to ignore Branch Specifiers in config.xml when being triggered by BitBucket Plugin Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Ivan Fernandez Calvo resolved as Fixed Jenkins / JENKINS-34958 Getting "Your Authorization Token has expired" when using ECR credentials Change By: Ivan Fernandez Calvo Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34437) Enable amazon-ecr-plugin behind proxy
Title: Message Title Ivan Fernandez Calvo resolved as Won't Fix Amazon ECR Plugin is a wrapper for AWS credentials to use with ECR does not manage connections. Jenkins / JENKINS-34437 Enable amazon-ecr-plugin behind proxy Change By: Ivan Fernandez Calvo Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-36127) ECR plugin throwing null pointer when attempt to configure docker build and publish
Title: Message Title Ivan Fernandez Calvo resolved as Fixed Jenkins / JENKINS-36127 ECR plugin throwing null pointer when attempt to configure docker build and publish Change By: Ivan Fernandez Calvo Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35323) Migrate amazon-ecr-plugin to 2.x parent pom
Title: Message Title Ivan Fernandez Calvo stopped work on JENKINS-35323 Change By: Ivan Fernandez Calvo Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35323) Migrate amazon-ecr-plugin to 2.x parent pom
Title: Message Title Ivan Fernandez Calvo resolved as Fixed Jenkins / JENKINS-35323 Migrate amazon-ecr-plugin to 2.x parent pom Change By: Ivan Fernandez Calvo Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38465) ECR plugin isn't compatible with credentials managed by folder plugin
Title: Message Title Ivan Fernandez Calvo updated JENKINS-38465 Jenkins / JENKINS-38465 ECR plugin isn't compatible with credentials managed by folder plugin Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38755) Merge Choice Parameter values more intelligently
Title: Message Title Marc Carter updated JENKINS-38755 Jenkins / JENKINS-38755 Merge Choice Parameter values more intelligently Change By: Marc Carter Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38755) Merge Choice Parameter values more intelligently
Title: Message Title Marc Carter edited a comment on JENKINS-38755 Re: Merge Choice Parameter values more intelligently Given that ABC represents a param with three choices and that the default choice is the first one (this is how they work internally), here's my plan:|| # || Template || Child || Result || Comment ||| 1 | ABC | ABC | ABC | no_change || 2 | ABC | CAB | CAB | reordering_is_retained || 3 | ABCD | ABC | ABCD | template_additions_are_added || 3b | ABCDE | BCE | ABCDE | template_additions_are_added_with_order_if_child_matches || 3c | ABCDE | DBC | DABCE ADBCE | template_additions_are_added_without_order_if_child_reordered || 4 | ABC | ABCD | ABCD | child_additions_are_retained || 4b | ABC | DABC | DABC | child_additions_are_retained_with_order || 5 | ABC | AB | ABC | child_removals_are_ignored_wrongly || 6 | AB | ABC | ABC | template_removals_are_ignored_wrongly |Note the last two are limitations because we do not know the change that was made, only the current state of template and child. This means a template-addition is exactly the same as a child-removal. Based on feedback, additions are of more value than removals. If you wish to propagate a removal then the user will need to remove the choice param entirely (which does propagate) then re-add it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38755) Merge Choice Parameter values more intelligently
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38755 Re: Merge Choice Parameter values more intelligently Code changed in jenkins User: Marc Carter Path: README.md src/main/java/com/joelj/jenkins/eztemplates/exclusion/JobParametersExclusion.java src/test/java/com/joelj/jenkins/eztemplates/exclusion/JobParametersExclusionTest.java http://jenkins-ci.org/commit/ez-templates-plugin/037088d8b0df2f63194f5ab8742b9804aa1d5b6e Log: Feature: JENKINS-38755 Merge Choice Parameter values more intelligently Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38465) ECR plugin isn't compatible with credentials managed by folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38465 Re: ECR plugin isn't compatible with credentials managed by folder plugin Code changed in jenkins User: Ivan Fernandez Calvo Path: src/main/java/com/cloudbees/jenkins/plugins/amazonecr/AmazonECSRegistryCredential.java src/main/java/com/cloudbees/jenkins/plugins/amazonecr/AmazonECSRegistryCredentialsProvider.java http://jenkins-ci.org/commit/amazon-ecr-plugin/6eee172bd9cdc2351bed9cc32228cf8ebbeaa63a Log: Merge pull request #7 from kuisathaverat/JENKINS-38465 [FIX JENKINS-38465] it now search credentials also into folders Compare: https://github.com/jenkinsci/amazon-ecr-plugin/compare/1e9f9237825d...6eee172bd9cd Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38465) ECR plugin isn't compatible with credentials managed by folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38465 Re: ECR plugin isn't compatible with credentials managed by folder plugin Code changed in jenkins User: Ivan Fernandez Calvo Path: src/main/java/com/cloudbees/jenkins/plugins/amazonecr/AmazonECSRegistryCredential.java src/main/java/com/cloudbees/jenkins/plugins/amazonecr/AmazonECSRegistryCredentialsProvider.java http://jenkins-ci.org/commit/amazon-ecr-plugin/7572ce2975f9c5a8ebc8a2509fd980dd6a979dd9 Log: JENKINS-38465 it now search credentials also into folders Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39361) LDAP SSL authentication isn't working with OpenJDK 8/Oracle JDK 8
Title: Message Title Alex Grinko created an issue Jenkins / JENKINS-39361 LDAP SSL authentication isn't working with OpenJDK 8/Oracle JDK 8 Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ldap-plugin Created: 2016/Oct/28 10:56 PM Priority: Minor Reporter: Alex Grinko We configured LDAPS authentication and it works fine with OpenJDK 7. Once we switched to OpenJDK 8 or Oracle JDK 8 we got following error: Oct 28, 2016 10:40:30 PM hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl bind WARNING: Failed to bind to dc2.xxx.com:3269 javax.naming.CommunicationException: simple bind failed: dc2.xxx.com:3269 [Root exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Certificates does not conform to algorithm constraints] at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:219) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2788) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2696) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2670) at com.sun.jndi.ldap.LdapCtx.reconnect(LdapCtx.java:2666) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:673) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:578) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:282) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:265) at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) at
[JIRA] (JENKINS-30274) ADFS Integration - What claims to use?
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-30274 ADFS Integration - What claims to use? Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33526) Support generation of the SAML metadata that can be consumed by IdPs
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-33526 Support generation of the SAML metadata that can be consumed by IdPs Change By: Ivan Fernandez Calvo Assignee: Benjamin Zaiser Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33526) Support generation of the SAML metadata that can be consumed by IdPs
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ben McCann Jenkins / JENKINS-33526 Support generation of the SAML metadata that can be consumed by IdPs Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Ben McCann Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33526) Support generation of the SAML metadata that can be consumed by IdPs
Title: Message Title Ivan Fernandez Calvo assigned an issue to Benjamin Zaiser Jenkins / JENKINS-33526 Support generation of the SAML metadata that can be consumed by IdPs Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Benjamin Zaiser Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34813) SAML2 plugin not working when https is terminated in load balancer
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-34813 SAML2 plugin not working when https is terminated in load balancer Change By: Ivan Fernandez Calvo Assignee: Ben McCann Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37311) "logout" link doesn't work
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-37311 "logout" link doesn't work Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34867) Jenkins SAML SSO issue
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-34867 Jenkins SAML SSO issue Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33526) Support generation of the SAML metadata that can be consumed by IdPs
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-33526 Support generation of the SAML metadata that can be consumed by IdPs Change By: Ivan Fernandez Calvo Assignee: Ben McCann Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35434) Wiki is out-of-sync with 0.5
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-35434 Wiki is out-of-sync with 0.5 Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36373) SAML Plugin Disappears when Jenkins is restarted
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-36373 SAML Plugin Disappears when Jenkins is restarted Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34283) Can't access Okta Group Info in SAML2 response
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-34283 Can't access Okta Group Info in SAML2 response Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37289) authentication issue instant is too old or in the future
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-37289 authentication issue instant is too old or in the future Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36274) SamlException when using SAML-plugin on securityRealm/finishLogin
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-36274 SamlException when using SAML-plugin on securityRealm/finishLogin Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38971) Add support SAML ForceAuthn, AuthnContextClassRef, custom EntityId, and session timeout
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-38971 Add support SAML ForceAuthn, AuthnContextClassRef, custom EntityId, and session timeout Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38625) SAML authentication only works in incognito mode
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-38625 SAML authentication only works in incognito mode Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38034) SAML Plugin does not load groups when access with API Token
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-38034 SAML Plugin does not load groups when access with API Token Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34437) Enable amazon-ecr-plugin behind proxy
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-34437 Enable amazon-ecr-plugin behind proxy Change By: Ivan Fernandez Calvo Assignee: Nicolas De Loof Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38779) Group Attribute while setting up Saml SSO
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-38779 Group Attribute while setting up Saml SSO Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-38228 Incorrect implementation of `loadUserByUsename`, Users are added on demand Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-34958 Getting "Your Authorization Token has expired" when using ECR credentials Change By: Ivan Fernandez Calvo Assignee: Nicolas De Loof Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37320) SAML SSO plugin change - Enable Unified Jenkins profile config for SSO
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-37320 SAML SSO plugin change - Enable Unified Jenkins profile config for SSO Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36189) Credentials from instance profile?
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-36189 Credentials from instance profile? Change By: Ivan Fernandez Calvo Assignee: Nicolas De Loof Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36127) ECR plugin throwing null pointer when attempt to configure docker build and publish
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-36127 ECR plugin throwing null pointer when attempt to configure docker build and publish Change By: Ivan Fernandez Calvo Assignee: Nicolas De Loof Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36890) PR's do not meet the criteria when Include Branches is set
Title: Message Title mcrooney commented on JENKINS-36890 Re: PR's do not meet the criteria when Include Branches is set We are also seeing this. There doesn't appear to be any help text for those include/exclude fields so I'm not sure how this is supposed to work. We'd also like something like "master PR*". Antonio Muñiz, should this be working or are we specifying this pattern incorrectly? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34188) jenkins.log noise: "script parameter ... is not an instance of Java.util.Map."
Title: Message Title Bruno P. Kinoshita commented on JENKINS-34188 Re: jenkins.log noise: "script parameter ... is not an instance of Java.util.Map." The master branch has already a few fixes, and we are now working on tickets like JENKINS-38889, which we can ship quite soon. A hotfix with just this fix is doable, but I would rather wait to release everything in the next days. The plug-in is part of the BioUno project. And we will have a project meeting on November 18th. I just replied the meeting announcement e-mail from Ioannis Moutsatsos suggesting to cut a release before the meeting, and another release before the end of the year - https://groups.google.com/forum/#!topic/biouno-users/2Scg0u6V3kM So if, besides this ticket, there are any other features/bugs that you would like to get shipped in the next releases, just reply here or join the hangout Cheers B Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32624) sshagent{} ignored when executed in docker.image().inside{...}
Title: Message Title
Jesse Glick commented on JENKINS-32624
Re: sshagent{} ignored when executed in docker.image().inside{...}
The previous naming pattern for branch projects can be restored with a system property, see release notes.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26057) Workflow build step for Maven
Title: Message Title Jesse Glick commented on JENKINS-26057 Re: Workflow build step for Maven It is in a separate plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33210) EOFException when using Static Analysis Collector
Title: Message Title Vlad Lapadatescu commented on JENKINS-33210 Re: EOFException when using Static Analysis Collector Thank you! This actually solved my problem as well! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26057) Workflow build step for Maven
Title: Message Title davidkarlsen commented on JENKINS-26057 Re: Workflow build step for Maven What version will this be in? I found no commit references Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32624) sshagent{} ignored when executed in docker.image().inside{...}
Title: Message Title
Joshua Spiewak commented on JENKINS-32624
Re: sshagent{} ignored when executed in docker.image().inside{...}
I am referring to the previous behavior that stored the workspace in sub-folders without the base32 of the hash that was introduced for JENKINS-34564.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38809) "rbenv build wrapper" disabled after Jenkins restart
Title: Message Title Stacy Brock commented on JENKINS-38809 Re: "rbenv build wrapper" disabled after Jenkins restart We are also seeing this issue in Jenkins 2.27, rbenv-plugin 0.0.17. It's accompanied by an "Unreadable Data" notification in Manage Old Data: Type: hudson.model.FreeStyleProject Name: (our job name) Error: NoSuchMethodError: org.jruby.RubyClass.getVariableAccessorForWrite(Ljava/lang/String;)Lorg/jruby/RubyClass$VariableAccessor;, CannotResolveClassException: rbenv_repository, CannotResolveClassException: ruby_build_revision, CannotResolveClassException: rbenv_root, CannotResolveClassException: version, CannotResolveClassException: rbenv_revision, CannotResolveClassException: gem_list, CannotResolveClassException: configure_opts, CannotResolveClassException: ignore_local_version, CannotResolveClassException: ruby_configure_opts, InstantiationError: null, MissingFieldException: No field 'pluginid' found in class 'hudson.model.FreeStyleProject' Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32000) durable-task 1.7 breaks workflow bat steps
Title: Message Title
Jesse Glick commented on JENKINS-32000
Re: durable-task 1.7 breaks workflow bat steps
One user reported similar symptoms which seem to have been caused by writing
env.PATH = "${tool 'Maven 3'}/bin:${env.PATH}"
rather than
env.Path = "${tool 'Maven 3'}\\bin;${env.Path}"
(The bad path separator : is the problem; the rest is stylistic.) An implementation of JENKINS-28718 would offer a cross-platform version of this idiom not susceptible to that mistake. At any rate, WindowsBatchScript could detect a node whose current %Path% lacks C:\Windows\System32 or generally does not seem to have an entry for cmd.exe, and report this misconfiguration more clearly.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38530) incorrect verdict when processing reports in parallel
Title: Message Title Alberto Gomez-Estrada edited a comment on JENKINS-38530 Re: incorrect verdict when processing reports in parallel Are we sure that this is a bug with the code and not inadequate documentation?I encountered a similar issue, and upon testing, I noticed the following behavior:If the threshold for UNSTABLE is set to N, then the test will have a SUCCESS value up until N - 1 FAILS.If the threshold for FAILED is set to N, then the test will have a SUCCESS or UNSTABLE value up until N - 1 FAILS.I haven't looked at the source code, but this feels like more of an issue with the documentation being unclear on how this feature works. *Note about parallel builds*I also have two tests running in parallel. I noticed that the xml that xUnit was parsing for each of the test results had the same "title" value, despite the filenames being different. This caused xUnit to overwrite the first file it parsed, and only report the results of the second file. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38636) JiraTestResultReporter-plugin: does not work on Jenkins 2.X+
Title: Message Title Alberto Gomez-Estrada commented on JENKINS-38636 Re: JiraTestResultReporter-plugin: does not work on Jenkins 2.X+ Can confirm that I've also run into this issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38530) incorrect verdict when processing reports in parallel
Title: Message Title Alberto Gomez-Estrada commented on JENKINS-38530 Re: incorrect verdict when processing reports in parallel Are we sure that this is a bug with the code and not inadequate documentation? I encountered a similar issue, and upon testing, I noticed the following behavior: If the threshold for UNSTABLE is set to N, then the test will have a SUCCESS value up until N - 1 FAILS. If the threshold for FAILED is set to N, then the test will have a SUCCESS or UNSTABLE value up until N - 1 FAILS. I haven't looked at the source code, but this feels like more of an issue with the documentation being unclear on how this feature works. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32000) durable-task 1.7 breaks workflow bat steps
Title: Message Title Jesse Glick commented on JENKINS-32000 Re: durable-task 1.7 breaks workflow bat steps Christoph Vogtländer Are you using the EnvInject plugin? If so, disable it. At any rate, if there are steps to reproduce from scratch please let us know. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38603) Coverity Plugin 1.8.0 fails on cov-analyze - intermediate directory contains no translation units
Title: Message Title Jonathan Strickland commented on JENKINS-38603 Re: Coverity Plugin 1.8.0 fails on cov-analyze - intermediate directory contains no translation units Thanks, we will try this in our next go round of staging upgrades. We have multiple Coverity jobs (hosting 10+ projects on our server) thus we would have to plan for this to upgrade and reconfigure the appropriate jobs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39360) Allow ALLOWED_JNLPJARS_FILES to be configurable by plugins
Title: Message Title Antonio Beyah created an issue Jenkins / JENKINS-39360 Allow ALLOWED_JNLPJARS_FILES to be configurable by plugins Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: core, swarm-plugin Created: 2016/Oct/28 6:11 PM Priority: Minor Reporter: Antonio Beyah We currently use the [Swarm](https://wiki.jenkins-ci.org/display/JENKINS/Swarm+Plugin) plugin to configure our agents to connect to the master and one of the things we have to do is presetup the agent with the proper version of the swarm-client jar. One thing I wanted to do was update the swarm plugin to allow you to retrieve the swarm-client.jar in the same manner as we can the slave.jar. When I looked at the code though I don't think this is possible due to the code in the core. The current process looks like this: Download swarm-client.jar from internet Download slave.jar from master Run java process with -cp slave.jar:swarm-client.jar I would like it to look like: Download swarm-client.jar from master Download slave.jar from master Run java process with -cp slave.jar:swarm-client.jar End goal is to allow me to configure my agents by retrieving any necessary components from the master, including plugin client dependencies such as the swarm-client.jar. References:
[JIRA] (JENKINS-14761) Backslash broken on Properties Content injection
Title: Message Title Jon Starbird closed an issue as Done reopened in error. Closing again. Jenkins / JENKINS-14761 Backslash broken on Properties Content injection Change By: Jon Starbird Status: Reopened Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14761) Backslash broken on Properties Content injection
Title: Message Title Jon Starbird commented on JENKINS-14761 Re: Backslash broken on Properties Content injection Apologies, I just saw your old note about the changes for backslash handling. Somehow I missed the message about the changes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14761) Backslash broken on Properties Content injection
Title: Message Title Jon Starbird edited a comment on JENKINS-14761 Re: Backslash broken on Properties Content injection This is broken again in 1.93.1 and 1 . 93. Properties like name=somevalue\someothervalue get imported as somevaluesomeothervalue Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14761) Backslash broken on Properties Content injection
Title: Message Title Jon Starbird reopened an issue This is broken again in 1.93.1. Properties like name=somevalue\someothervalue get imported as somevaluesomeothervalue Jenkins / JENKINS-14761 Backslash broken on Properties Content injection Change By: Jon Starbird Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Sam Van Oort commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Jesse Glick For the case of ABORTED, typically this is set not due to a call to Run.setResult inside the script, but rather the program as a whole terminating with FlowInterruptedException. (That API supports any Result, but ABORTED is the most common.) In such cases you can tell where the exception was thrown by inspecting ErrorAction. Thanks, that is a proposal that might solve that aspect. I think my concern is that we're building up a set of fairly complex rules now for what is the "status" of a FlowNode. Rather than doing that, we should just add a status coding (probably JENKINS-26522) and have steps set it where needed – we can cut out so much complexity very fast, and give more data and control to the user. > Where in blueocean we want to repot per set status by computing if that step had any error or it's still running or not. So, we still do this with the StatusAndTiming APIs – if you want to hide the uncertain UNSTABLE assignment until there's a better mechanism for attributing it, one solution is to coerce UNSTABLE status to SUCCESS (completed) in your mapping (always legal IIRC). > I guess I need more context here, just so that blueocean can unblock it Primarily that Stage View would be the logical case to demo a new JENKINS-26522 API in the UI and we don't do enhancements to it generally now. However if we just did explicit status coding with this and not tags / other metadata, then that's purely a change to pipeline-graph-analysis plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-24513) Zero executors on master not well documented or enforced
Title: Message Title Jesse Glick commented on JENKINS-24513 Re: Zero executors on master not well documented or enforced If you have not configured a queue item authenticator then builds which succeeded before would begin failing. Which could be considered a good thing—security is now being enforced—but on the other hand would be a nasty surprise in an upgrade. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38092) workflow-multibranch plugin doesn't use credentials when indexing the branches
Title: Message Title Jesse Glick commented on JENKINS-38092 Re: workflow-multibranch plugin doesn't use credentials when indexing the branches Incomplete suggests that there's not enough information to fix the defect Exactly. In general for problems involving an external service, which are unlikely to be easily reproducible in a self-contained environment, you would need to track down the root problem yourself. I have done just that Not in the stack trace in the issue description—that is showing the plain Git branch source. You want to install the aforementioned plugin and use its branch source instead. You can use the plain Git branch source with BitBucket, but the performance and features will be inferior. If this is a known problem There is no bug in this area that I am aware of. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-38679) Polling using legacy SCM fails: “Workspace doesn't contain https://svn/global-library-repo${library.myib.version}”
Title: Message Title
Jesse Glick commented on JENKINS-38679
Re: Polling using legacy SCM fails: “Workspace doesn't contain https://svn/global-library-repo${library.myib.version}”
Dunno, will have to see if it is reproducible in a functional test when I have some time.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39199) Null pointer exception when new build triggered and jenkins tries to create new DO slave
Title: Message Title Bogdan Padalko commented on JENKINS-39199 Re: Null pointer exception when new build triggered and jenkins tries to create new DO slave After reinstalling plugin the issue gone, however, it would be nice to hear from someone whether it is false-positive or not. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-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." Could you do a release just to fix this? It's literally 90% of the logs for my entire jenkins server. (or maybe a log4j guru could provide a config to filter this spam) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39251) Multibranch-Multiconfiguration project workspace path not following folder structure layout
Title: Message Title Jesse Glick commented on JENKINS-39251 Re: Multibranch-Multiconfiguration project workspace path not following folder structure layout configurable via system property, see version history of branch-api Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Vivek Pandey commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Thanks Sam Van Oort. >I'm not sure why you're saying that the status and timing APIs are the problem here – how would you propose I work around the data model limitation? I didn't say StatusAndtiming is a problem. What I meant was, these API doesn't give how blueocean wants to repot per state status. For example, if overall run is UNSTABLE, this API will give UNSTABLE for all steps. Where in blueocean we want to repot per set status by computing if that step had any error or it's still running or not. >No, a stage/parallel is a FAILURE if the final node in it had an error – otherwise the error was handled in a try/catch block. This was the same mistake that legacy Stage View made. Unfortunately Jesse Glick shot down my proposal to properly track this status in pipeline since this is not the best way to handle this. Yes, makes sense. >The right way to handle this is definitely JENKINS-26522 + step-level support for its custom statuses, but unfortunately that has been blocked by Blue Ocean itself. I guess I need more context here, just so that blueocean can unblock it Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39329) exception in phase 'semantic analysis' in source unit 'WorkflowScript' exception in phase 'canonicalization' in source unit: When using Abstract Class in Global Shared Library
Title: Message Title Jesse Glick assigned an issue to Stephan Pauxberger Jenkins / JENKINS-39329 exception in phase 'semantic analysis' in source unit 'WorkflowScript' exception in phase 'canonicalization' in source unit: When using Abstract Class in Global Shared Library Change By: Jesse Glick Assignee: Jesse Glick Stephan Pauxberger Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39329) exception in phase 'semantic analysis' in source unit 'WorkflowScript' exception in phase 'canonicalization' in source unit: When using Abstract Class in Global Shared Library
Title: Message Title Jesse Glick updated JENKINS-39329 Jenkins / JENKINS-39329 exception in phase 'semantic analysis' in source unit 'WorkflowScript' exception in phase 'canonicalization' in source unit: When using Abstract Class in Global Shared Library Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39329) exception in phase 'semantic analysis' in source unit 'WorkflowScript' exception in phase 'canonicalization' in source unit: When using Abstract Class in Global Shared Library
Title: Message Title Jesse Glick started work on JENKINS-39329 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39329) exception in phase 'semantic analysis' in source unit 'WorkflowScript' exception in phase 'canonicalization' in source unit: When using Abstract Class in Global Shared Library
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39329 exception in phase 'semantic analysis' in source unit 'WorkflowScript' exception in phase 'canonicalization' in source unit: When using Abstract Class in Global Shared Library Change By: Jesse Glick Component/s: workflow-cps-global-lib-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Jesse Glick commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should There's no way for the pipeline to identify which step set the build status to unstable Well, if the script just ran currentBuild.result = 'UNSTABLE' or a step called Run.setResult that is true; we would need a proper implementation of JENKINS-26522. (I am only opposed to partial implementations which do not actually update at least one UI to use the capability.) More likely we would want JENKINS-27395, which is what would accomplish the actual goal specified in the initial issue description here. In fact I think this is just a duplicate. Again the issue is not implementing the step & data model, which is trivial, but deciding which UIs should interpret that data and how. For the case of ABORTED, typically this is set not due to a call to Run.setResult inside the script, but rather the program as a whole terminating with FlowInterruptedException. (That API supports any Result, but ABORTED is the most common.) In such cases you can tell where the exception was thrown by inspecting ErrorAction. Keith Zantow I would point out that this idiom from the master branch makes no sense at all. You could just delete the try and finally blocks and the result would still be FAILURE—but more easily analyzed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-34560) Need to know how to trigger a build based on commit message text.
Title: Message Title Fathi Boudra resolved as Fixed Jenkins / JENKINS-34560 Need to know how to trigger a build based on commit message text. Change By: Fathi Boudra Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39359) Tool Locations published from swarm client on windows are appended with forward slash
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-39359
Tool Locations published from swarm client on windows are appended with forward slash
Change By:
Alexander Komarov
I publish tool locations for preinstalled tools on my windows-based swarm clients using the command-line args, and until recently this worked fine . (presumably with previous versions of jenkins and plugins) Today (haven't used these jobs in a while) I see this in the output (I run "echo Path is %PATH%" in a Windows batch step){quote}>echo "Path is *e:\jenkins\jdk\JDK_1.7/bin*;c:\tools\apache-maven-3.0.5\bin\;e:\jenkins\jdk\JDK_1.7/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;E:\cygwin64\bin;E:\jenkins\bin;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\SlikSvn\bin;e:\jenkins\ant\apache-ant-1.9.7\bin;C:\Program Files (x86)\MSBuild\12.0\Bin;e:\jenkins\maven\apache-maven-3.2.5\bin;e:\jenkins\jdk\JDK_1.8\bin;;c:\tools\;C:\Windows\Microsoft.NET\Framework\v4.0.30319" {quote}The PATH is prepended with the JDK bin path which is incorrect. The path shows up correctly on the slave's Configure screen, see screenshot.I don't know for certain whether it is the swarm plugin or jenkins tool provider core doing this.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34560) Need to know how to trigger a build based on commit message text.
Title: Message Title
Fathi Boudra edited a comment on JENKINS-34560
Re: Need to know how to trigger a build based on commit message text.
In your job, under the build trigger section: gerrit event -> trigger on -> add -> comment added contains regular _expression_ -> value -> {noformat} .*TriggerCiBuild.* {noformat} Note: I changed the commit message triggering the build to make it easier to write the regex. You still need to configure the gerrit project, see https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger#GerritTrigger-TriggerConfiguration
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39359) Tool Locations published from swarm client on windows are appended with forward slash
Title: Message Title
Alexander Komarov edited a comment on JENKINS-39359
Re: Tool Locations published from swarm client on windows are appended with forward slash
As a workaround I replace / with \ like this in the batch step: {code:java} PATH="%PATH:/=\%"{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39359) Tool Locations published from swarm client on windows are appended with forward slash
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-39359
Tool Locations published from swarm client on windows are appended with forward slash
Change By:
Alexander Komarov
I publish tool locations for preinstalled tools on my windows-based swarm clients using the command-line args, and until recently this worked fine.Today (haven't used these jobs in a while) I see this in the output (I run "echo Path is %PATH%" in a Windows batch step) {quote} >echo "Path is *e:\jenkins\jdk\JDK_1.7/bin*;c:\tools\apache-maven-3.0.5\bin\;e:\jenkins\jdk\JDK_1.7/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;E:\cygwin64\bin;E:\jenkins\bin;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\SlikSvn\bin;e:\jenkins\ant\apache-ant-1.9.7\bin;C:\Program Files (x86)\MSBuild\12.0\Bin;e:\jenkins\maven\apache-maven-3.2.5\bin;e:\jenkins\jdk\JDK_1.8\bin;;c:\tools\;C:\Windows\Microsoft.NET\Framework\v4.0.30319"{quote} The PATH is prepended with the JDK bin path which is incorrect. The path shows up correctly on the slave's Configure screen, see screenshot.I don't know for certain whether it is the swarm plugin or jenkins tool provider core doing this.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39359) Tool Locations published from swarm client on windows are appended with forward slash
Title: Message Title Alexander Komarov commented on JENKINS-39359 Re: Tool Locations published from swarm client on windows are appended with forward slash As a workaround I replace / with \ like this in the batch step: PATH="%PATH:/=%" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34560) Need to know how to trigger a build based on commit message text.
Title: Message Title Fathi Boudra commented on JENKINS-34560 Re: Need to know how to trigger a build based on commit message text. In your job, under the build trigger section: gerrit event -> trigger on -> add -> comment added contains regular _expression_ -> value -> .TriggerCiBuild. You still need to configure the gerrit project, see https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger#GerritTrigger-TriggerConfiguration Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39359) Tool Locations published from swarm client on windows are appended with forward slash
Title: Message Title Alexander Komarov created an issue Jenkins / JENKINS-39359 Tool Locations published from swarm client on windows are appended with forward slash Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: Screenshot_2016-10-28_12-44-31.png Components: swarm-plugin Created: 2016/Oct/28 4:51 PM Environment: Jenkins Master: version 2.26 Linux JDK 1.7 for the JVM Swarm plugin 2.2 Slave: Swarm jar 2.0 Windows 2008 Priority: Minor Reporter: Alexander Komarov I publish tool locations for preinstalled tools on my windows-based swarm clients using the command-line args, and until recently this worked fine. Today (haven't used these jobs in a while) I see this in the output (I run "echo Path is %PATH%" in a Windows batch step) >echo "Path is e:\jenkins\jdk\JDK_1.7/bin;c:\tools\apache-maven-3.0.5\bin\;e:\jenkins\jdk\JDK_1.7/bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;E:\cygwin64\bin;E:\jenkins\bin;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\SlikSvn\bin;e:\jenkins\ant\apache-ant-1.9.7\bin;C:\Program Files (x86)\MSBuild\12.0\Bin;e:\jenkins\maven\apache-maven-3.2.5\bin;e:\jenkins\jdk\JDK_1.8\bin;;c:\tools\;C:\Windows\Microsoft.NET\Framework\v4.0.30319" The PATH is prepended with the JDK bin path which is incorrect. The path shows up correctly on the slave's Configure screen, see screenshot. I don't know for certain whether it is the
[JIRA] (JENKINS-39010) Comment Added event does not work
Title: Message Title Fathi Boudra commented on JENKINS-39010 Re: Comment Added event does not work Similar regression. Jobs used to work with 2.20.0 version. After upgrading to 2.22.0 version, it doesn't work anymore. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34560) Need to know how to trigger a build based on commit message text.
Title: Message Title Fathi Boudra updated an issue Jenkins / JENKINS-34560 Need to know how to trigger a build based on commit message text. Change By: Fathi Boudra Priority: Blocker Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39296) Regression: Shell step failed but step marked as successful
Title: Message Title Vivek Pandey updated JENKINS-39296 Jenkins / JENKINS-39296 Regression: Shell step failed but step marked as successful Change By: Vivek Pandey Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39334) Unable to run script.sh using "Execute shell script on remote host using ssh"
Title: Message Title Jimmy Vo commented on JENKINS-39334 Re: Unable to run script.sh using "Execute shell script on remote host using ssh" I try to test it as you advise: cd /Path-To-File/bin/ ./windchill shell sh -xe /Path-To-File/cbif/setup.sh -Dcbif.install.zip=/Path-To-File/Patch.zip -Dcbif.install.quiet=true -Dcbif.install.noRestart=true -Dcbif.install.phaseTwoOnly=true -Dcbif.install.force=true The result is that it still runs forerver. It shows it is spinning and running without any error on the Console Output. When I check for the install-log folder in the Slave node, it doesn't generate any new install-log file. When I execute the same commands on the slave node directly, it works good. Thank you Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
