[JIRA] (JENKINS-38262) Jenkins can't visit update-center
Title: Message Title binhui wang updated an issue Jenkins / JENKINS-38262 Jenkins can't visit update-center Change By: binhui wang Environment: windows jenkins 2. 7 .4 ,windows7 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38262) Jenkins can't visit update-center
Title: Message Title binhui wang assigned an issue to Oleg Nenashev Jenkins / JENKINS-38262 Jenkins can't visit update-center Change By: binhui wang Assignee: binhui wang Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38262) Jenkins can't visit update-center
Title: Message Title binhui wang updated an issue Jenkins / JENKINS-38262 Jenkins can't visit update-center Change By: binhui wang Attachment: screenshot-3.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38262) Jenkins can't visit update-center
Title: Message Title binhui wang updated an issue Jenkins / JENKINS-38262 Jenkins can't visit update-center Change By: binhui wang 1.When i install jenkins on my computer, it can't visit update-center.2.In the steup of installing plugins, it says the Jenkins instance appears to be offline.See screenshot-13.I skip this steup,and go to plugins manager to visit update-center.It show me some exceptions. See screenshot-24.I visit the url( http://updates.jenkins-ci.org/update-center.json ) in browser(chrome) , and it redirect i can dowload the json file but the browser is redirected tohttps://mirrors.tuna.tsinghua.edu.cn/jenkins/updates/current/update-center.json . See screenshot-3 how can i reslove this problem? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you 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-38262) Jenkins can't visit update-center
Title: Message Title binhui wang updated an issue Jenkins / JENKINS-38262 Jenkins can't visit update-center Change By: binhui wang 1.When i install jenkins on my computer, it can't visit update-center.2.In the steup of installing plugins, it says the Jenkins instance appears to be offline.Seescreenshot-13. I skip this steup,and go to plugins manager to visit update-center.It show some exceptions. See screenshot-2 4.I visit the url(),and it redirect to how can i reslove this problem? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38262) Jenkins can't visit update-center
Title: Message Title binhui wang updated an issue Jenkins / JENKINS-38262 Jenkins can't visit update-center Change By: binhui wang Attachment: screenshot-2.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38262) Jenkins can't visit update-center
Title: Message Title binhui wang updated an issue Jenkins / JENKINS-38262 Jenkins can't visit update-center Change By: binhui wang Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38262) Jenkins can't visit update-center
Title: Message Title binhui wang created an issue Jenkins / JENKINS-38262 Jenkins can't visit update-center Issue Type: Bug Assignee: binhui wang Attachments: screenshot-1.png Components: _unsorted Created: 2016/Sep/16 5:00 AM Environment: windows 7 Priority: Critical Reporter: binhui wang 1.When i install jenkins on my computer, it can't visit update-center. 2.In the steup of installing plugins, it says the Jenkins instance appears to be offline.See I skip this steup,and go to plugins manager to visit update-center.It show some exceptions. Add Comment
[JIRA] (JENKINS-38198) Jenkins and Maven SOA BPEL project deployment issue
Title: Message Title Atul Gupta closed an issue as Fixed Identified my issue. So closing this issue Jenkins / JENKINS-38198 Jenkins and Maven SOA BPEL project deployment issue Change By: Atul Gupta Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38241) Show git commit message in build log
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-38241 Show git commit message in build log 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-24661) vSphere Cloud Deploy VM from Template - Requires snapshot of template, not possible in vSphere 5.5
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24661 Re: vSphere Cloud Deploy VM from Template - Requires snapshot of template, not possible in vSphere 5.5 Code changed in jenkins User: Jason Swager Path: src/main/java/org/jenkinsci/plugins/vsphere/builders/Deploy.java http://jenkins-ci.org/commit/vsphere-cloud-plugin/ef95e6f6fcf9777997b8eb4b95d862af0026b99f Log: Merge pull request #52 from pjdarton/fix_jenkins_24605 Fix JENKINS-24605 and JENKINS-24661 Compare: https://github.com/jenkinsci/vsphere-cloud-plugin/compare/cf3f8a8f8c0f...ef95e6f6fcf9 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38249) Deploy VM from template fails to obtain IP when VM is off
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38249 Re: Deploy VM from template fails to obtain IP when VM is off Code changed in jenkins User: Jason Swager Path: src/main/java/org/jenkinsci/plugins/vsphere/builders/Deploy.java src/main/resources/org/jenkinsci/plugins/vsphere/builders/Deploy/help-powerOn.html src/main/resources/org/jenkinsci/plugins/vsphere/builders/Deploy/help-template.html http://jenkins-ci.org/commit/vsphere-cloud-plugin/cf3f8a8f8c0f6a976cd4ce93e9ffa2e04b17bc2c Log: Merge pull request #51 from pjdarton/fix_jenkins_38249 Fix for JENKINS-38249 Compare: https://github.com/jenkinsci/vsphere-cloud-plugin/compare/8d97ef18a9cf...cf3f8a8f8c0f Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38261) 503 error Service not available after installin AnsiColor+Plugin
Title: Message Title Ketan Desai created an issue Jenkins / JENKINS-38261 503 error Service not available after installin AnsiColor+Plugin Issue Type: Story Assignee: Unassigned Components: ansicolor-plugin Created: 2016/Sep/16 3:10 AM Environment: 1.5 ant antisamy-markup-formatter antisamy-markup-formatter.bak antisamy-markup-formatter.jpi antisamy-markup-formatter.jpi.pinned ant.jpi authorize-project authorize-project.jpi build-failure-analyzer build-failure-analyzer.jpi build-pipeline-plugin build-pipeline-plugin.jpi build-user-vars-plugin build-user-vars-plugin.jpi copyartifact copyartifact.bak copyartifact.jpi credentials credentials.bak credentials.jpi credentials.jpi.pinned cvs cvs.jpi cvs.jpi.disabled delivery-pipeline-plugin delivery-pipeline-plugin.jpi email-ext email-ext.jpi email-ext-recipients-column email-ext-recipients-column.jpi external-monitor-job external-monitor-job.jpi flexible-publish flexible-publish.jpi git git.bak git-client git-client.bak git-client.jpi github-api github-api.bak github-api.jpi git.jpi greenballs greenballs.jpi groovy icon-shim icon-shim.jpi javadoc javadoc.bak javadoc.jpi javadoc.jpi.pinned jquery jquery.jpi jquery-ui jquery-ui.jpi junit junit.jpi ldap ldap.bak ldap.jpi ldap.jpi.pinned ls.out mailer mailer.bak mailer.jpi mailer.jpi.pinned mail-watcher-plugin mail-watcher-plugin.jpi mapdb-api mapdb-api.jpi matrix-auth matrix-auth.bak matrix-auth.jpi matrix-auth.jpi.pinned matrix-project matrix-project.bak matrix-project.jpi matrix-project.jpi.pinned maven-plugin maven-plugin.bak maven-plugin.jpi maven-plugin.jpi.pinned pam-auth pam-auth.bak pam-auth.jpi pam-auth.jpi.pinned parameterized-trigger parameterized-trigger.jpi publish-over-ftp publish-over-ftp.jpi publish-over-ssh publish-over-ssh.jpi run-condition run-condition.jpi schedule-build schedule-build.jpi scm-api scm-api.jpi script-security script-security.jpi skip-certificate-check skip-certificate-check.jpi ssh-credentials ssh-credentials.bak ssh-credentials.jpi ssh-credentials.jpi.pinned ssh-slaves ssh-slaves.bak ssh-slaves.jpi ssh-slaves.jpi.pinned subversion subversion.bak subversion.jpi subversion.jpi.pinned token-macro token-macro.jpi translation translation.bak translation.jpi translation.jpi.pinned URLSCM URLSCM.jpi windows-slaves windows-slaves.jpi windows-slaves.jpi.disabled Priority:
[JIRA] (JENKINS-38261) 503 error Service not available after installing AnsiColor+Plugin
Title: Message Title Ketan Desai updated an issue Jenkins / JENKINS-38261 503 error Service not available after installing AnsiColor+Plugin Change By: Ketan Desai Summary: 503 error Service not available after installin installing AnsiColor+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-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory
Title: Message Title Jacob Keller commented on JENKINS-32479 Re: multiple git repositories sometimes fail to checkout some of them into subdirectory Unfortunately this would still result in the same problem, because the git plugin wipes out the workspace when cloning, so it is still possible to have the issue occur. It is easier to avoid in the pipeline as long as the pipeline steps are ordered correctly. The user just has to know and understand that the git plugin will wipe out the workspace path so you must ensure that the repositories are ordered correctly. In general, for pipeline this is obvious, but it is not obvious for the multi-scm 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-13634) Multiple SCM plugin fails when used with matrix project and git plugin
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-13634 Multiple SCM plugin fails when used with matrix project and git plugin Change By: Craig Rodrigues 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
[JIRA] (JENKINS-13779) Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM)
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-13779 Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM) Change By: Craig Rodrigues 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
[JIRA] (JENKINS-22390) Multiple SCM plugin thinks there are changes when there are not
Title: Message Title Craig Rodrigues resolved as Won't Fix Jenkins / JENKINS-22390 Multiple SCM plugin thinks there are changes when there are not Change By: Craig Rodrigues Status: Reopened 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22390) Multiple SCM plugin thinks there are changes when there are not
Title: Message Title Craig Rodrigues reopened an issue Jenkins / JENKINS-22390 Multiple SCM plugin thinks there are changes when there are not Change By: Craig Rodrigues 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22390) Multiple SCM plugin thinks there are changes when there are not
Title: Message Title Craig Rodrigues resolved as Fixed Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-22390 Multiple SCM plugin thinks there are changes when there are not Change By: Craig Rodrigues 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
[JIRA] (JENKINS-30667) poll scm always run even there is no changes with multiple scm plugin configured two branches in the same repo
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-30667 poll scm always run even there is no changes with multiple scm plugin configured two branches in the same repo Change By: Craig Rodrigues 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"
[JIRA] (JENKINS-13000) Git repositories (git plugin 1.1.15) used within Jenkins multiple SCMs plugin (0.2) are not detected by the remote-trigger hook functionality
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-13000 Git repositories (git plugin 1.1.15) used within Jenkins multiple SCMs plugin (0.2) are not detected by the remote-trigger hook functionality Change By: Craig Rodrigues 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
[JIRA] (JENKINS-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-32479 multiple git repositories sometimes fail to checkout some of them into subdirectory Change By: Craig Rodrigues 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
[JIRA] (JENKINS-31934) Split changelog by repository when using the multiple SCM plugin
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-31934 Split changelog by repository when using the multiple SCM plugin Change By: Craig Rodrigues 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
[JIRA] (JENKINS-34895) Multiple SCMs plugin doesn't save file system path
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-34895 Multiple SCMs plugin doesn't save file system path Change By: Craig Rodrigues 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
[JIRA] (JENKINS-9287) Configuration is not saven when two git repositories are added
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-9287 Configuration is not saven when two git repositories are added Change By: Craig Rodrigues 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
[JIRA] (JENKINS-14883) MultiSCM with Mercurial doesn't tell which repos the changesets came from
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-14883 MultiSCM with Mercurial doesn't tell which repos the changesets came from Change By: Craig Rodrigues 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
[JIRA] (JENKINS-14019) Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-14019 Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building Change By: Craig Rodrigues 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
[JIRA] (JENKINS-33824) Multiple SCMs (all git repos) where one repo should not trigger a build still causes a build to be triggered
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-33824 Multiple SCMs (all git repos) where one repo should not trigger a build still causes a build to be triggered Change By: Craig Rodrigues 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"
[JIRA] (JENKINS-34271) Cannot Retrieve Commit Hashes when Using Multiple Get Repositories
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-34271 Cannot Retrieve Commit Hashes when Using Multiple Get Repositories Change By: Craig Rodrigues 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
[JIRA] (JENKINS-35080) Multi SCMs Starting Build With Every Poll
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-35080 Multi SCMs Starting Build With Every Poll Change By: Craig Rodrigues 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
[JIRA] (JENKINS-36003) Multiple SCM does'nt support Subversion 1.8
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-36003 Multiple SCM does'nt support Subversion 1.8 Change By: Craig Rodrigues 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
[JIRA] (JENKINS-37114) “Changes” in Jenkins build are empty
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-37114 “Changes” in Jenkins build are empty Change By: Craig Rodrigues 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,
[JIRA] (JENKINS-38113) Multiple SCMs Git repositories checks out wrong SHA.
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-38113 Multiple SCMs Git repositories checks out wrong SHA. Change By: Craig Rodrigues 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
[JIRA] (JENKINS-27470) StackOverflowError with version 0.4
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-27470 StackOverflowError with version 0.4 Change By: Craig Rodrigues 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
[JIRA] (JENKINS-26645) Multiple SCM plugin
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-26645 Multiple SCM plugin Change By: Craig Rodrigues 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
[JIRA] (JENKINS-27409) adding base clearcase on multiple scm plugin causes exceptions even for basic configuration
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-27409 adding base clearcase on multiple scm plugin causes exceptions even for basic configuration Change By: Craig Rodrigues 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
[JIRA] (JENKINS-29425) Multiple SCM + Mercurial + Git
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-29425 Multiple SCM + Mercurial + Git Change By: Craig Rodrigues 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
[JIRA] (JENKINS-34766) String index out of range in MultiSCMRevisionState.keyFor
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-34766 String index out of range in MultiSCMRevisionState.keyFor Change By: Craig Rodrigues 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
[JIRA] (JENKINS-34841) Add Multiple SCM TFS Label Support
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-34841 Add Multiple SCM TFS Label Support Change By: Craig Rodrigues 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
[JIRA] (JENKINS-34962) Multiple SCM plugin not create separate repo manifest.
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to Pipeline plugin, which offers a supported way of checking out from multiple scms https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-34962 Multiple SCM plugin not create separate repo manifest. Change By: Craig Rodrigues 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
[JIRA] (JENKINS-35496) Multiple SCM doesn't provide changes for a build
Title: Message Title Craig Rodrigues resolved as Won't Fix Suggest that you migrate to using the Pipeline plugin, which offers a supported way of checking out from multiple SCMS: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Jenkins / JENKINS-35496 Multiple SCM doesn't provide changes for a build Change By: Craig Rodrigues 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
[JIRA] (JENKINS-38252) SSE channel registration takes long time
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38252 SSE channel registration takes long time Change By: Michael Neale Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38251) Fetching favorited items for a user is very slow
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38251 Fetching favorited items for a user is very slow Change By: Michael Neale Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38253) Optimize static resource fetch
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38253 Optimize static resource fetch Change By: Michael Neale Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26107) Allow stage to operate as a labelled block
Title: Message Title
Michael Neale commented on JENKINS-26107
Re: Allow stage to operate as a labelled block
mohamed badran by code do you mean pipeline itself? If so:
stage "first"
sh "echo 42"
echo "hey"
would become:
stage("first") {
sh "echo 42"
echo "hey"
}
that is about all there is to 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-38229) Null pointer exception causing No jobs to be executed and just stalls saying "Waiting for next available executor"
Title: Message Title Arun V commented on JENKINS-38229 Re: Null pointer exception causing No jobs to be executed and just stalls saying "Waiting for next available executor" Also this seems similar to https://issues.jenkins-ci.org/browse/JENKINS-24008 But we are already using " Build With Parameters Plugin". And the job was manually triggered from jenkins UI. Any help is greatly appreciated. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38226) Radiator view based on favourited pipelines
Title: Message Title Michael Neale commented on JENKINS-38226 Re: Radiator view based on favourited pipelines James Dumay great! also depends how comfortable your seat is on the way home... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36057) API to retrieve unbuilt commits for a branch
Title: Message Title Jesse Glick commented on JENKINS-36057 Re: API to retrieve unbuilt commits for a branch An API already exists for listing SCMRevision between a build currently running and the current branch head, but not to get any metadata for these such as commit message. GitHub offers an API to retrieve commit info but it seems there is no facility for batching this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38229) Null pointer exception causing No jobs to be executed and just stalls saying "Waiting for next available executor"
Title: Message Title Arun V updated an issue Jenkins / JENKINS-38229 Null pointer exception causing No jobs to be executed and just stalls saying "Waiting for next available executor" Change By: Arun V Summary: jenkins master not executing Null pointer exception causing No jobs on master to be executed and slaves and just stalls saying "Waiting for next available executor" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Vivek Pandey commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly Yes absolutely, bismuth is coming soon to BO in very near future Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Michael Neale commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly Right, well the changes for steps has been merged so that is good, and thorsten has a proposed fix. Vivek Pandey all the more reason to move to bismuth at some point I think right Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33274) "Base build" link for first build of branch project
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-33274 "Base build" link for first build of branch project Change By: Jesse Glick Assignee: stephenconnolly Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title Christian Höltje edited a comment on JENKINS-38111 Re: github organization should allow 'clean before checkout' behavior They cannot be read without triggering the need for a lot of accept approvals. See the linked issue: JENKINS-37817 for the list the last time I tried. That list grew as of yesterday's versions of things. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title Christian Höltje commented on JENKINS-38111 Re: github organization should allow 'clean before checkout' behavior They cannot be read without triggering the need for a lot of accept approvals. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34814) Trigger build parameters not getting passed downstream
Title: Message Title Zaur Salam commented on JENKINS-34814 Re: Trigger build parameters not getting passed downstream vi /etc/sysconfig/jenkins Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title Jesse Glick commented on JENKINS-37324 Re: We would like a more meaningful description of a step via flow nodes Possibly “for free” from JENKINS-31582. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-37324 We would like a more meaningful description of a step via flow nodes Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38259) "IllegalArgumentException: folder must not be null" when cloning vm
Title: Message Title Greg Smith updated an issue Jenkins / JENKINS-38259 "IllegalArgumentException: folder must not be null" when cloning vm Change By: Greg Smith Priority: Minor Trivial Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26340) Implement SimpleBuildStep for Pipeline Compatibility
Title: Message Title James Nord resolved as Fixed released as 0.9.something Jenkins / JENKINS-26340 Implement SimpleBuildStep for Pipeline Compatibility Change By: James Nord Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26340) Implement SimpleBuildStep for Pipeline Compatibility
Title: Message Title James Nord closed an issue as Fixed Jenkins / JENKINS-26340 Implement SimpleBuildStep for Pipeline Compatibility Change By: James Nord Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title Mark Waite edited a comment on JENKINS-38111 Re: github organization should allow 'clean before checkout' behavior Those can all be set through the checkout() step. They may also be accessible from the scm object. I've not experimented with trying to use them from the scm object. If I find a way to read the existing value from teh the scm object so that it can be reused in the checkout() step, I'll certainly post it here. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title
Mark Waite edited a comment on JENKINS-38111
Re: github organization should allow 'clean before checkout' behavior
[~ spotty docwhat ] when you say that people need "per-repository control", do you mean that they want a setting which controls all repositories within the entire organization (in my case, that would be "git-plugin", "git-client-plugin", and "jenkins-bugs"), or would it be a setting per repository (one each for "git-plugin", "git-client-plugin", and "jenkins-bugs"), or would it be a setting per branch ("git-plugin:master", "git-plugin:3.0.0-beta", etc.)? I assumed from the phrase "per-repository" that you meant one for each repository in the organization. If that is the case, then doesn't that mean that the definition needs to be associated to each repository? I'm not sure how we would associate the definition to a repository, since currently the Jenkinsfile is per branch. I guess we could declare that the "per-repository" control is the Jenkinsfile which comes from the master branch, though the git purists will likely complain that master is just a convention, not a mandate.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title Mark Waite commented on JENKINS-38111 Re: github organization should allow 'clean before checkout' behavior Those can all be set through the checkout() step. They may also be accessible from the scm object. I've not experimented with trying to use them from the scm object. If I find a way to read the existing value from teh scm object so that it can be reused in the checkout() step, I'll certainly post it here. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title
Vivek Pandey commented on JENKINS-37338
Re: Pipeline scripts that should appear in /queue are returned in /runs API
Cliff Meyers: >My understanding is that all pipelines basically begin running immediately, so could we assume that the build number returned for a pipeline is reliable? If not, what scenario would this not hold true in? Generally yes, pipeline almost immediately get the run id. However in certain cases where you are throttling a pipeline build, it will end up in queue. For example try this pipeline script and click on build now few times and you will see it ends up in queue:
node {
echo 'Hello World'
properties([[$class: 'JobPropertyImpl', throttle: [count: 1, durationName: 'hour']], pipelineTriggers([])])
}
>For freestyle jobs, my understanding is that there can be only one item in the queue at once. No, you can have any number of items in queue for the same pipeline jobs. Each with its own projected/estimated build id and queue id - these are queued items. >Similarly then could we assume that the build number would be "eventually correct" once the item in the queue actually moves to the run state? yes. >I don't know enough about other job types (e.g. Matrix) to know if there would be problems there. jobs resulting from matrix jobs could be either pipeline or regular jobs so same rules apply. we are not displaying them so we can hold off on them for now.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38260) Kubernetes plugin does not respect Container Cap
Title: Message Title Jonathan Rogers created an issue Jenkins / JENKINS-38260 Kubernetes plugin does not respect Container Cap Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Sep/15 10:17 PM Environment: Jenkins 2.7.1 Kubernetes plugin 0.8 Priority: Minor Reporter: Jonathan Rogers The Kubernetes plugin frequently creates more concurrent slaves than the number set in the "Container Cap" field. Add Comment
[JIRA] (JENKINS-38075) Github Plugin build strategy improvement
Title: Message Title Christian Stewart commented on JENKINS-38075 Re: Github Plugin build strategy improvement I have the same things happen... Also: new commits in PRs are not automatically built, the hook seems to be ignored I have to click "scan branches" pretty frequently Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38259) "IllegalArgumentException: folder must not be null" when cloning vm
Title: Message Title Greg Smith created an issue Jenkins / JENKINS-38259 "IllegalArgumentException: folder must not be null" when cloning vm Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2016/Sep/15 10:06 PM Environment: Jenkins 2.21 vSphere Plugin 2.13 Priority: Minor Reporter: Greg Smith While trying to create a new clone / slave, instead of the vm being cloned, the following error is being thrown: Provisioned agent MacOS10.10Slave-1 failed to launch org.jenkinsci.plugins.vsphere.tools.VSphereException: java.lang.IllegalArgumentException: folder must not be null. at org.jenkinsci.plugins.vsphere.tools.VSphere.cloneOrDeployVm(VSphere.java:169) at org.jenkinsci.plugins.vsphere.tools.VSphere.cloneVm(VSphere.java:129) at org.jenkinsci.plugins.vSphereCloudSlaveTemplate.provision(vSphereCloudSlaveTemplate.java:250) at org.jenkinsci.plugins.vSphereCloud$1.call(vSphereCloud.java:274) at org.jenkinsci.plugins.vSphereCloud$1.call(vSphereCloud.java:272) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.IllegalArgumentException: folder must not be null. at com.vmware.vim25.mo.VirtualMachine.cloneVM_Task(VirtualMachine.java:164) at org.jenkinsci.plugins.vsphere.tools.VSphere.cloneOrDeployVm(VSphere.java:158) ... 9 more I tracked down in the source where this was happening, and it looks like this line is the problem: ask task = sourceVm.cloneVM_Task((Folder) sourceVm.getParent(), cloneName, cloneSpec); So – "(Folder)
[JIRA] (JENKINS-38259) "IllegalArgumentException: folder must not be null" when cloning vm
Title: Message Title Greg Smith updated an issue Jenkins / JENKINS-38259 "IllegalArgumentException: folder must not be null" when cloning vm Change By: Greg Smith While trying to create a new clone / slave, instead of the vm being cloned, the following error is being thrown:Provisioned agent MacOS10.10Slave-1 failed to launchorg.jenkinsci.plugins.vsphere.tools.VSphereException: java.lang.IllegalArgumentException: folder must not be null. at org.jenkinsci.plugins.vsphere.tools.VSphere.cloneOrDeployVm(VSphere.java:169) at org.jenkinsci.plugins.vsphere.tools.VSphere.cloneVm(VSphere.java:129) at org.jenkinsci.plugins.vSphereCloudSlaveTemplate.provision(vSphereCloudSlaveTemplate.java:250) at org.jenkinsci.plugins.vSphereCloud$1.call(vSphereCloud.java:274) at org.jenkinsci.plugins.vSphereCloud$1.call(vSphereCloud.java:272) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.IllegalArgumentException: folder must not be null. at com.vmware.vim25.mo.VirtualMachine.cloneVM_Task(VirtualMachine.java:164) at org.jenkinsci.plugins.vsphere.tools.VSphere.cloneOrDeployVm(VSphere.java:158) ... 9 moreI tracked down in the source where this was happening, and it looks like this line is the problem: ask Task task = sourceVm.cloneVM_Task((Folder) sourceVm.getParent(),cloneName, cloneSpec);So -- "(Folder) sourceVm.getParent()" is returning null, and then the cloneVM_Task() function is checking that the folder is not null, and throwing this error.I am not sure under what circumstances .getParent() on the source VM is allowed to be null -- other clones of this same vm by the same ID, under similar api restraints is working fine -- its only failing in our Jenkins instance with the above stack trace. Add Comment
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title
Mark Waite edited a comment on JENKINS-33984
Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Yes, you would need to specify multiple refspecs behind the advanced button of the repository definition for the job. I assume your {noformat}origin/release**{noformat} branch specifier really means {noformat}origin/release/**{noformat}. I think your refspec should look like this:{noformat}+refs/heads/develop:refs/remotes/origin/develop+refs/heads/release/*:refs/remotes/origin/release/*{noformat}The [git refspecs documentation|https://git-scm.com/book/en/v2/Git-Internals-The-Refspec] gives a very good review of the strengths and weaknesses of refspec definition.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title
Mark Waite edited a comment on JENKINS-33984
Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Yes, you would need to specify multiple refspecs behind the advanced button of the repository definition for the job. I assume your {noformat}origin/release**{noformat} branch specifier really means { { noformat} origin/release/** {noformat } }: . I think your refspec should look like this: {noformat}+refs/heads/develop:refs/remotes/origin/develop+refs/heads/release/*:refs/remotes/origin/release/*{noformat}The [git refspecs documentation|https://git-scm.com/book/en/v2/Git-Internals-The-Refspec] gives a very good review of the strengths and weaknesses of refspec definition.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title
Mark Waite edited a comment on JENKINS-33984
Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Yes, you would need to specify multiple refspecs behind the advanced button of the repository definition for the job. I assume your { { noformat} origin/release** {noformat } } branch specifier really means {{origin/release/**}}:{noformat}+refs/heads/develop:refs/remotes/origin/develop+refs/heads/release/*:refs/remotes/origin/release/*{noformat}The [git refspecs documentation|https://git-scm.com/book/en/v2/Git-Internals-The-Refspec] gives a very good review of the strengths and weaknesses of refspec definition.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title
Mark Waite edited a comment on JENKINS-33984
Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Yes, you would need to specify multiple refspecs behind the advanced button of the repository definition for the job. I assume your ` {{ origin/release** ` }} branch specifier really means ` {{ origin/release/** ` }} :{noformat}+refs/heads/develop:refs/remotes/origin/develop+refs/heads/release/*:refs/remotes/origin/release/*{noformat}The [git refspecs documentation|https://git-scm.com/book/en/v2/Git-Internals-The-Refspec] gives a very good review of the strengths and weaknesses of refspec definition.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38258) covcomplplot-plugin unnecessarily depends on Subversion
Title: Message Title Dmitry Erastov updated an issue Jenkins / JENKINS-38258 covcomplplot-plugin unnecessarily depends on Subversion Change By: Dmitry Erastov I'd like to disable the Subversion plugin in my Jenkins installation, and the only plugin that's consuming it right now is the Coverage/Complexity Scatter Plot.I'm not an expert on how Jenkins plugins work, but it seems the sole reason for this is that the plugin's pom.xml [references ]( | https://github.com/jenkinsci/covcomplplot-plugin/blob/master/pom.xml#L40 ) ] an old svn repo for Powermock. This has since moved to Github, so it would seem that the repo URL needs to be updated (or removed, if the library is available from the core Jenkins repo). I didn't find any other references to Subversion in the plugin's source code.Can someone confirm this analysis? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title Mark Waite commented on JENKINS-33984 Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1) Yes, you would need to specify multiple refspecs behind the advanced button of the repository definition for the job. I assume your `origin/release*` branch specifier really means `origin/release/*`: +refs/heads/develop:refs/remotes/origin/develop +refs/heads/release/*:refs/remotes/origin/release/* The git refspecs documentation gives a very good review of the strengths and weaknesses of refspec definition. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38258) covcomplplot-plugin unnecessarily depends on Subversion
Title: Message Title Dmitry Erastov created an issue Jenkins / JENKINS-38258 covcomplplot-plugin unnecessarily depends on Subversion Issue Type: Bug Assignee: Unassigned Components: covcomplplot-plugin Created: 2016/Sep/15 9:40 PM Environment: Jenkins 2.22 Coverage/Complexity Scatter Plot PlugIn 1.1.1 Labels: subversion dependencies plugin coverage Priority: Minor Reporter: Dmitry Erastov I'd like to disable the Subversion plugin in my Jenkins installation, and the only plugin that's consuming it right now is the Coverage/Complexity Scatter Plot. I'm not an expert on how Jenkins plugins work, but it seems the sole reason for this is that the plugin's pom.xml [references](https://github.com/jenkinsci/covcomplplot-plugin/blob/master/pom.xml#L40) an old svn repo for Powermock. This has since moved to Github, so it would seem that the repo URL needs to be updated (or removed, if the library is available from the core Jenkins repo). I didn't find any other references to Subversion in the plugin's source code. Can someone confirm this analysis?
[JIRA] (JENKINS-37791) When running a pipeline from a favourite we should not move the card
Title: Message Title Cliff Meyers commented on JENKINS-37791 Re: When running a pipeline from a favourite we should not move the card I had to do a bunch of cleanup to the Favorites Cards now that the new Capabilities API is in place; decided to impl this too at the same time and found a solution I like that didn't require a huge amount of code to do this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37791) When running a pipeline from a favourite we should not move the card
Title: Message Title Cliff Meyers commented on JENKINS-37791 Re: When running a pipeline from a favourite we should not move the card PR: https://github.com/jenkinsci/blueocean-plugin/pull/502 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37791) When running a pipeline from a favourite we should not move the card
Title: Message Title Cliff Meyers updated JENKINS-37791 Jenkins / JENKINS-37791 When running a pipeline from a favourite we should not move the card Change By: Cliff Meyers Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26340) Implement SimpleBuildStep for Pipeline Compatibility
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26340 Re: Implement SimpleBuildStep for Pipeline Compatibility Code changed in jenkins User: James Nord Path: pom.xml src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/BackgroundResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/BeforeAfterResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONParser.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultAction.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultArchiver.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/DefaultTestResultParserImpl.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/FeatureResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/StepResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/TagResult.java src/test/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONParserTest.java src/test/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONSupportPluginIT.java src/test/resources/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONSupportPluginIT/featureFail.json src/test/resources/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONSupportPluginIT/featurePass.json src/test/resources/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioResultTest/cucumber-jvm_examples_java-calculator__cucumber-report.json http://jenkins-ci.org/commit/cucumber-testresult-plugin/d87afb14e45b754d023ca76f2d47e5e3e531780e Log: Merge pull request #8 from helloeve/master JENKINS-26340 Pipeline Integration Compare: https://github.com/jenkinsci/cucumber-testresult-plugin/compare/48dda7f1f2a7...d87afb14e45b Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-26430) non-administrators unable to manually provision new slaves
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26430 Re: non-administrators unable to manually provision new slaves Code changed in jenkins User: James Nord Path: pom.xml src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultAction.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultArchiver.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/TagResult.java src/test/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONParserTest.java src/test/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONSupportPluginIT.java src/test/resources/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioResultTest/cucumber-jvm_examples_java-calculator__cucumber-report.json http://jenkins-ci.org/commit/cucumber-testresult-plugin/cd792abaa1bb24ddf39021caff1a38c5bf668ca5 Log: JENKINS-26430 WIP pipeline compatability Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title ikedam commented on JENKINS-35081 Re: Separate authorization configuration page I found I mixed up several different problems and tried to resolve them at all. (I made those problems clear in JENKINS-38217) I now believe those problems can be resolved one-by-one. And it also told me that I no longer need to splitting configuration files: It relates not to the original purpose of separating the configuration page but rather to JENKINS-38219 (Restrict Job.CONFIGURE permissions by plugins). It doesn't work as expected until I resolve JENKINS-38219. And once after I resolve JENKINS-38219, I no longer need to split configuration files for security purposes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38217) Roadmap of authorize-project-plugin
Title: Message Title
ikedam updated an issue
Jenkins / JENKINS-38217
Roadmap of authorize-project-plugin
Change By:
ikedam
authorize-project-plugin have following issues for its design.* Authentications of the project during configuration and after configuration may change.** This makes it difficult for other plugins behave depending on authentications of projects.* The way to reject unauthenticated configurations is unstable.** authorize-project plugin should reject user A configure a project when the project is configured as user B.** The current implementation raises exception when saving unauthenticated configurfation.* Difficult to configure permissions of builds.** What users really want to do is to configure permissions of builds.*** This is why I named it "authorize-project".** {{QueueItemAuthenticator}} is designed to return {{Authentication}}, which can be considered a user.** And then, the current design of authorize-project is to configure builds run as a specific user.*** This might mean "authenticate-project" was more appropreate for the plugin name.** This causes following difficulties:*** There can be cases that administrators don't want to bind a project to an actual specific user. Alice and Bob belongs to DevOps group. They want run builds of a project as the permission of DevOps, but don't to run as Alice or Bob as they both want configure the project.*** There can be cases that administrators cannot define a new user for build authentications. E.g. Jenkins is configured to use an external user dictionary (e.g. Active Directory) and the administrator of Jenkins doesn't administer that directory.|| Issue || Resolution || JIRA ticket ||| Authentication may change when configuration | Split configuration page | JENKINS-35081 || Unstable way to reject unauthenticated configuration | Restrict CONFIGURE permission by plugins | JENKINS-38219 || Difficulties in configuring permissions | Introduce define additional build-in users | JENKINS-38257 |
Add Comment
[JIRA] (JENKINS-38257) Feature to define non-actual user
Title: Message Title ikedam created an issue Jenkins / JENKINS-38257 Feature to define non-actual user Issue Type: New Feature Assignee: ikedam Components: authorize-project-plugin, core Created: 2016/Sep/15 8:41 PM Priority: Minor Reporter: ikedam Authorize-project plugin has difficulties for its usage as it requires actual users to run builds as. It can easily conflicts with policies of administrators: Administrators might don't want to use an actual user for managing authorizations of builds. E.g. Alice and Bob belongs to a DevOps team. They want to run a project with the authorization of DevOps, but not of Alice or Bob. Because it might cause problems when they quit the job. This can be resolved by defining a non-actual user used only to manage authorizations of builds. Administrator doesn't want to define or can't define non-actual users. It can be the case especialy when they use an external authentication system (such as Active Directory). This can be resolved by introducing a feature to define non-actual users, just like build-in users such as ANONYMOUS and SYSTEM. They cannot be used to login Jenkins. (They don't have passwords)
[JIRA] (JENKINS-13035) Duplicate Views Tab Bar option
Title: Message Title Ignacio Albors closed an issue as Fixed Jenkins / JENKINS-13035 Duplicate Views Tab Bar option Change By: Ignacio Albors Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38219) Restrict Job.CONFIGURE permissions by plugins
Title: Message Title ikedam commented on JENKINS-38219 Re: Restrict Job.CONFIGURE permissions by plugins Macro supports in role-strategy-plugin might be helpful for this feature. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30840) "possible next launch" view column
Title: Message Title Ignacio Albors resolved as Fixed Done. It will be included in the next release. Jenkins / JENKINS-30840 "possible next launch" view column Change By: Ignacio Albors 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-30840) "possible next launch" view column
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30840 Re: "possible next launch" view column Code changed in jenkins User: Ignacio Albors Path: src/main/java/hudson/plugins/nextexecutions/columns/NextExecutionColumn.java src/main/java/hudson/plugins/nextexecutions/columns/PossibleNextExecutionColumn.java src/main/java/hudson/plugins/nextexecutions/utils/NextExecutionsUtils.java src/main/resources/hudson/plugins/nextexecutions/columns/Messages.properties http://jenkins-ci.org/commit/next-executions-plugin/fea6f926d4743aa194311c6fc6a5f7a64841bee0 Log: Added a column type with the next possible builds. It shows when the next scm polling will be done. If there is any scm change a new build will be launch. Fixes JENKINS-30840 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38205) Failed to deploy war on Weblogic: task completed abnormally (exit code = 1)
Title: Message Title
Guillermo Figueroa commented on JENKINS-38205
Re: Failed to deploy war on Weblogic: task completed abnormally (exit code = 1)
Raphael, Apparently the problem is related to the image of Jenkins for docker, because I tried a similar environment (Jenkins 2.7.2, plugin weblogic-deployer-plugin 3.5, WebLogic 12.2.1 and JDK 8), but jenkins (jenkins.war) deployed on WebLogic (Machine X), and deployment tasks were performed without error in the weblogic server (Machine Y). This is the log: Building in workspace /app/wlsadm12/.jenkins/workspace/job-deploy-weblogic-test [WeblogicDeploymentPlugin] - Pay attention to JDK version {selected version is 1.8.0_74} compatibility with WebLogic Deployer API (see Oracle documentation). [WeblogicDeploymentPlugin] - The JDK /opt/oracle/jdk1.8.0_74/jre will be used. [WeblogicDeploymentPlugin] - Retrieving artifacts recorded [filtered resources on testcicd.war]... [WeblogicDeploymentPlugin] - 2 files found under wls-deploy-plugin [WeblogicDeploymentPlugin] - the following resource recorded /app/wlsadm12/.jenkins/wls-deploy-plugin/testcicd.war is eligible. [WeblogicDeploymentPlugin] - the following resource ['plugin-configuration.xml'] doesn't match testcicd.war [WeblogicDeploymentPlugin] - Deploying the artifact on the following target : (name=wls-alpha) (host=57.228.138.211) (port=12100) [WeblogicDeploymentPlugin] - UNDEPLOYING ARTIFACT... $ /opt/oracle/jdk1.8.0_74/jre/bin/java -Xms256M -Xmx256M -cp /opt/oracle/wls12.2.1/wlserver/server/lib/weblogic.jar weblogic.Deployer -debug -remote -verbose -noexit -name testcicd -targets Admin -adminurl t3://57.228.138.211:12100 -user system -password weblogic12 -undeploy [WeblogicDeploymentPlugin] - ARTIFACT UNDEPLOYED SUCCESSFULLY. [WeblogicDeploymentPlugin] - DEPLOYING ARTIFACT... $ /opt/oracle/jdk1.8.0_74/jre/bin/java -Xms256M -Xmx256M -cp /opt/oracle/wls12.2.1/wlserver/server/lib/weblogic.jar weblogic.Deployer -debug -stage -remote -verbose -upload -name testcicd -source /app/wlsadm12/.jenkins/wls-deploy-plugin/testcicd.war -targets Admin -adminurl t3://57.228.138.211:12100 -user system -password weblogic12 -deploy [WeblogicDeploymentPlugin] - ARTIFACT DEPLOYED SUCCESSFULLY. [INFO] [INFO] DEPLOYMENT SUCCESS [INFO] Finished: SUCCESS
Add Comment
[JIRA] (JENKINS-38254) Plugin impacted by SECURITY-170
Title: Message Title Pavel Dotsulenko started work on JENKINS-38254 Change By: Pavel Dotsulenko 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-38254) Plugin impacted by SECURITY-170
Title: Message Title Pavel Dotsulenko commented on JENKINS-38254 Re: Plugin impacted by SECURITY-170 Hi Daniel Pfeiffer, thanks for the report! We are working on a fix and we'll notify you as soon as new plugin version is released. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33552) Settings validation fails on JiraRestService.getMyPermissions()
Title: Message Title Radek Antoniuk commented on JENKINS-33552 Re: Settings validation fails on JiraRestService.getMyPermissions() What JIRA and jira-plugin versions? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title Pragya Jaiswal commented on JENKINS-33984 Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1) Thanks Mark for the explanation. Could you please elaborate on the using custom refspecs? I eventually have to extend my Jenkins job for the following Branch specifiers: Branch specifier 1 - origin/develop Branch Specifier 2 - origin/release** (But would like to ignore these set of branches - origin/feature** and origin/bugfix**) Would that require specifying multiple refspecs? Would you have a screenshot to share? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38111) github organization should allow 'clean before checkout' behavior
Title: Message Title Christian Höltje commented on JENKINS-38111 Re: github organization should allow 'clean before checkout' behavior By "per repository" I guess I really meant "per branch". Specifically, control it via a Jenkinsfile. Ideally by modifying the scm object or creating a copy in a simple way (not by copying every element one by one). Some examples that I have been recently asked about: Shallow clones Altering timeouts Clean before/after checkouts Calculate Changelog against specific branch etc. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36220) BlueOcean should show failing builds in main list view
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36220 BlueOcean should show failing builds in main list view Change By: James Dumay Labels: blueocean Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Vivek Pandey commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly >Vivek Pandey does bismuth help with this at all or will just show the same incorrect state? Michael Neale I looked at Bismuth API, it does not call FlowNode.isRunning() so it never encountered this bug, instead it assumes if endNode in branch is present, then the parallel branch run is over. Not a terrible assumption but would like to validate with Jesse on that ticket as possible workaround before putting in my 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-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title Mark Waite commented on JENKINS-33984 Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1) Sorry Pragya Jaiswal, but I don't have any ideas for fixing it. I suspect that the git plugin has a separation between the logic which decides which branches should be checked for changes, and which branches should be built. The git plugin generally assumes that once a SHA1 or one of its successors has been built, it does not need to be built again. I realize that is incorrect in this case, since the user clearly stated to check one set of branches, and the plugin incorrectly performed the checkout of a branch which was not in that set of branches. You might consider using one or more custom "refspec" values in the advanced section of the job's "Repositories" section. It may be that you can avoid the checkout of the develop branch by creating one or more refspecs which exclude the develop branch from being cloned into the repository. If the develop branch is not cloned into the repository, the plugin probably won't choose it as the branch to checkout. If you use the custom refspec technique, you'll also need to add the "Advanced clone option" (from "Additional Behaviours") to "Honor refspec on initial clone". The default behavior is to clone all remote refspecs, even if a custom refspec is provided. That default behavior is retained so that we don't break compatibility with some existing use cases. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title Nick Romanyshyn edited a comment on JENKINS-12783 Re: Delete workspace before build starts ignores Exlude patterns (for directories) I don't know if this applies to the OP, but I had a very similar issue. I specified patterns to exclude, but it would completely delete everything in the workspace. If I instead specified a pattern to include that would work as expected. In my case the exclude actually was working correctly. I verified this by adding a custom delete command which was just a simple python script that appended the name of the file to be deleted to a text file (so it didn't actually do any deleting). It turned out that I wasn't excluding the .git directory, so that was getting deleted. You can't clone into a non empty directory, so Jenkins had to remove the workspace completely in order to do a new clone. I haven't tried with .svn, but I would expect similar results. One other thing to note is that if that you don't specify an include pattern then the plugin automatically uses the pattern \ **/* So if you have included anything that doesn't match the .git directory that will also spare it from deletion.*tl;dr Make sure you also exclude your .git directory* Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title Nick Romanyshyn edited a comment on JENKINS-12783 Re: Delete workspace before build starts ignores Exlude patterns (for directories) I don't know if this applies to the OP, but I had a very similar issue. I specified patterns to exclude, but it would completely delete everything in the workspace. If I instead specified a pattern to include that would work as expected. In my case the exclude actually was working correctly. I verified this by adding a custom delete command which was just a simple python script that appended the name of the file to be deleted to a text file (so it didn't actually do any deleting). It turned out that I wasn't excluding the .git directory, so that was getting deleted. You can't clone into a non empty directory, so Jenkins had to remove the workspace completely in order to do a new clone. I haven't tried with .svn, but I would expect similar results. One other thing to note is that if that you don't specify an include pattern then the plugin automatically uses the pattern \ ** * /* * So if you have included anything that doesn't match the .git directory that will also spare it from deletion.*tl;dr Make sure you also exclude your .git directory* Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title Nick Romanyshyn commented on JENKINS-12783 Re: Delete workspace before build starts ignores Exlude patterns (for directories) I don't know if this applies to the OP, but I had a very similar issue. I specified patterns to exclude, but it would completely delete everything in the workspace. If I instead specified a pattern to include that would work as expected. In my case the exclude actually was working correctly. I verified this by adding a custom delete command which was just a simple python script that appended the name of the file to be deleted to a text file (so it didn't actually do any deleting). It turned out that I wasn't excluding the .git directory, so that was getting deleted. You can't clone into a non empty directory, so Jenkins had to remove the workspace completely in order to do a new clone. I haven't tried with .svn, but I would expect similar results. One other thing to note is that if that you don't specify an include pattern then the plugin automatically uses the pattern */ So if you have included anything that doesn't match the .git directory that will also spare it from deletion. tl;dr Make sure you also exclude your .git directory Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
