[JIRA] (JENKINS-39997) Bitbucket Build Status Notifier Plugin not reporting build status when job is in folder
Title: Message Title benoit guerin commented on JENKINS-39997 Re: Bitbucket Build Status Notifier Plugin not reporting build status when job is in folder hg or git ? if hg, maybe https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/pull/33 ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38974) Comment Added event crashes with NullPointerException
Title: Message Title Dan C commented on JENKINS-38974 Re: Comment Added event crashes with NullPointerException BTW the above commit from Andres Rodriguez seems to be totally unrelated... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40023) JGit changelog list no changes prior to merge commit
Title: Message Title
tzafrir updated an issue
Jenkins / JENKINS-40023
JGit changelog list no changes prior to merge commit
Change By:
tzafrir
git-client version 2.1.0 Adding Jgit changelog does not work well when setting max revisions limit, if the below test case in GitAPITestCase revisions containt merge commits . java fails with JGit but passes with CliGit. For JGit it seems that after That is because RevWalker check will only return the merge commit at HEAD number of revision as set by limitations , it finds no prior commits but ChangelogCommand default behaviour is to list and show skip merge commits. Resulting in returning less commits then requested by the changelog user . Whereas This can be seen by the CliGit does find below test case (for GitApiTestCase class) where JGit returns empty changelog if the head commit with the message "commit1" is a merge commit, and returns it's SHA1 max limit was set to 1. The test will pass if the max limit is increased to 2. {code}public void test_changelog_with_merge_commit test_changelog_with_merge_commit_and_max_log_history () throws Exception {w.init();w.commitEmpty("init");// First commit to branch1w.git.branch("branch1");w.git.checkout("branch1");w.touch("file1", "content1");w.git.add("file1");w.git.commit("commit1");String commitSha1 = w.git.revParse("HEAD").name();// Merge branch1 into masterw.git.checkout("master");String mergeMessage = "Merge message to be tested.";w.git.merge().setMessage(mergeMessage).setGitPluginFastForwardMode(MergeCommand.GitPluginFastForwardMode.NO_FF).setRevisionToMerge(w.git.getHeadRev(w.repoPath(), "branch1")).execute(); // Obtain last commit messageString mergeSha1 StringWriter writer = new StringWriter(); w.git. revParse changelog ( "HEAD" ). name max ( 1 ) .to(writer).execute() ; // Changing max limit to 2 will pass the test check_changelog_sha1 assertThat ( commitSha1 writer.toString() , "master" not(isEmptyString( ) )) ;} {code}
Add Comment
[JIRA] (JENKINS-40023) JGit changelog max limit not working well with merge commits
Title: Message Title tzafrir updated an issue Jenkins / JENKINS-40023 JGit changelog max limit not working well with merge commits Change By: tzafrir Summary: JGit changelog list no changes prior to max limit not working well with merge commit commits Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36041) default ldap timeouts are inappropriate
Title: Message Title Félix Belzunce Arcos started work on JENKINS-36041 Change By: Félix Belzunce Arcos 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-36041) default ldap timeouts are inappropriate
Title: Message Title Félix Belzunce Arcos assigned an issue to Félix Belzunce Arcos Jenkins / JENKINS-36041 default ldap timeouts are inappropriate Change By: Félix Belzunce Arcos Assignee: Félix Belzunce Arcos Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36041) default ldap timeouts are inappropriate
Title: Message Title Félix Belzunce Arcos updated JENKINS-36041 Jenkins / JENKINS-36041 default ldap timeouts are inappropriate Change By: Félix Belzunce Arcos Status: Reopened 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-40029) Sometime build triggered does not gets killed and it went into a hang state
Title: Message Title manish garg created an issue Jenkins / JENKINS-40029 Sometime build triggered does not gets killed and it went into a hang state Issue Type: Bug Assignee: Oleg Nenashev Attachments: jenkins.txt Components: _unsorted, build-with-parameters-plugin Created: 2016/Nov/25 7:12 AM Environment: Jenkins ver. 1.636, linux Red hat 6, google chrome, JDK 7 Priority: Major Reporter: manish garg Sometime when i Triger a build using build with parameters option it goes in to hang state. It doesnot gets killed even force killed doesnot work. So to kill I need to take a restart of jenkins. Please tell us the reason of it. I am attaching error log below. Add Comment
[JIRA] (JENKINS-38974) Comment Added event crashes with NullPointerException
Title: Message Title Dan C commented on JENKINS-38974 Re: Comment Added event crashes with NullPointerException Here is a PR including reproducer: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/301 Not sure if that's really the best place for the test though... Also, this has the downside of still requiring every job definition to be re-saved in order to avoid the NPE. I wonder if it might also be worthwhile to be defensive on the opposite side when handling the comment-added event, to use PLAIN if the option is set to null? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38974) Comment Added event crashes with NullPointerException
Title: Message Title Dan C commented on JENKINS-38974 Re: Comment Added event crashes with NullPointerException Scratch that... doesn't require every job to be re-saved, I didn't realise that that readResolve() method magically fixes up any existing job definitions when the plugin is upgraded. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38912) SEVERE: Exception thrown during event handling
Title: Message Title Dan C commented on JENKINS-38912 Re: SEVERE: Exception thrown during event handling Looks like a dupe of JENKINS-38974 ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38974) Comment Added event crashes with NullPointerException
Title: Message Title
Dan C commented on JENKINS-38974
Re: Comment Added event crashes with NullPointerException
The problem seems to be that is missing from existing job definitions. It's also not filled in by the plugin when an XML job definition is saved (for example when using Jenkins Job Builder, which doesn't generate any of the *ParameterMode elements). When that option is missing from the job definition the getter is returning null which means that commentTextMode is null in this block:
if (event instanceof CommentAdded) {
String comment = ((CommentAdded)event).getComment();
if (comment != null) {
commentTextMode.setOrCreateParameterValue(GERRIT_EVENT_COMMENT_TEXT,
parameters, comment, ParameterMode.PlainMode.TEXT, escapeQuotes);
}
}
I see that in commit e94a36e0 there is some special handling for changeSubjectParameterMode, when it was added, to ensure that the default is filled in to the job definition. I guess a similar thing should have been done for commentTextParameterMode.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You 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-40010) Jenkins Doesn’t open/launch Firefox with default user profile.
Title: Message Title Nethra P updated an issue Jenkins / JENKINS-40010 Jenkins Doesn’t open/launch Firefox with default user profile. Change By: Nethra P Attachment: FireFoxAuthentiation.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-40010) Jenkins Doesn’t open/launch Firefox with default user profile.
Title: Message Title Nethra P commented on JENKINS-40010 Re: Jenkins Doesn’t open/launch Firefox with default user profile. Hi, I think Issue is when Jenkins try to open FireFox (It is not calling by FireFox Porfile) Not with Selenium Plug-in. Go to Start -> Run -> firefox.exe -p -> Create FirefoxProfile. (in prefs.js file I set some Proxy details) I am doing this because of my System / Browser has Security Policies Enabled. Due to this whenever I ran other URL, proxy pop-up comes. For this reason I have created the FireFox Profile and the Set the proxies there. When I ran locally it is working fine. But the same script when I ran from Jenkins it is asking for pop-up. I am sorry I have selected wrong Component. Can anyone help me in getting Right Component about FireFox? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38386) Can't propagate "Build when a change is pushed to BitBucket" to all branches
Title: Message Title Matthew DeTullio resolved as Won't Fix You shouldn't need to do anything. Indexing will poll for changes and automatically trigger builds if changes were pushed. In addition, this plugin uses trigger functionality as defined by the branch-api-plugin, which does not offer all the standard freestyle triggers. No changes are planned in that regard. Jenkins / JENKINS-38386 Can't propagate "Build when a change is pushed to BitBucket" to all branches Change By: Matthew DeTullio Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38688) Multibranch: allow build to be triggered on duplicated branch project
Title: Message Title Matthew DeTullio assigned an issue to Unassigned Jenkins / JENKINS-38688 Multibranch: allow build to be triggered on duplicated branch project Change By: Matthew DeTullio Assignee: Matthew DeTullio Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38688) Multibranch: allow build to be triggered on duplicated branch project
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-38688 Multibranch: allow build to be triggered on duplicated branch project Change By: Matthew DeTullio Component/s: workflow-multibranch-plugin Component/s: multi-branch-project-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-32246) Is it absolutely necessary to keep full .git repository in the sub-projects?
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-32246 Is it absolutely necessary to keep full .git repository in the sub-projects? Change By: Matthew DeTullio Component/s: branch-api-plugin Component/s: scm-api-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-39532) NPE while using warning plugin pipeline snipped generator
Title: Message Title Matthew DeTullio assigned an issue to Ulli Hafner Jenkins / JENKINS-39532 NPE while using warning plugin pipeline snipped generator Change By: Matthew DeTullio Assignee: Matthew DeTullio Ulli Hafner Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39532) NPE while using warning plugin pipeline snipped generator
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-39532 NPE while using warning plugin pipeline snipped generator Change By: Matthew DeTullio Component/s: workflow-multibranch-plugin Component/s: multi-branch-project-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-37500) scm-syn-configurtaion issues with multi branch project
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-37500 scm-syn-configurtaion issues with multi branch project Change By: Matthew DeTullio Component/s: branch-api-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-37500) scm-syn-configurtaion issues with multi branch project
Title: Message Title Matthew DeTullio assigned an issue to Frédéric Camblor Jenkins / JENKINS-37500 scm-syn-configurtaion issues with multi branch project Change By: Matthew DeTullio Assignee: Matthew DeTullio Frédéric Camblor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37500) scm-syn-configurtaion issues with multi branch project
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-37500 scm-syn-configurtaion issues with multi branch project Change By: Matthew DeTullio Component/s: multi-branch-project-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-39926) No Gitlab configuration in Build Triggers
Title: Message Title Matthew DeTullio resolved as Won't Fix This is intended. The latest version of the plugin now only relies on triggers provided by the branch-api-plugin. There won't be any new changes regarding this except for to be compatible with the branch-api-plugin. Jenkins / JENKINS-39926 No Gitlab configuration in Build Triggers Change By: Matthew DeTullio 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-38837) Mutibranch project plugin does not respect "Workspace Root Directory" global configuration
Title: Message Title Matthew DeTullio assigned an issue to Stephen Connolly Jenkins / JENKINS-38837 Mutibranch project plugin does not respect "Workspace Root Directory" global configuration Change By: Matthew DeTullio Assignee: Matthew DeTullio Stephen Connolly Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38837) Mutibranch project plugin does not respect "Workspace Root Directory" global configuration
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-38837 Mutibranch project plugin does not respect "Workspace Root Directory" global configuration Change By: Matthew DeTullio Component/s: multi-branch-project-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-37495) [REGRESSION] Git Submodules having a name different to their path in working tree, failing to checkout
Title: Message Title Ethan Trewhitt edited a comment on JENKINS-37495 Re: [REGRESSION] Git Submodules having a name different to their path in working tree, failing to checkout I've created a pull request that should address this issue:https://github.com/jenkinsci/git-client-plugin/pull/ 224 225 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37419) Git plugin checking out non-existent submodule from different branch
Title: Message Title Ethan Trewhitt updated an issue Jenkins / JENKINS-37419 Git plugin checking out non-existent submodule from different branch Change By: Ethan Trewhitt Comment: I've committed a pull request that attempts to fix this bug. It pulls from .gitmodules rather than the repo-level git config. That file should be up-to-date with only the list of modules active in the current branch/commit/HEAD.https://github.com/jenkinsci/git-client-plugin/pull/224 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39533) no graph displayed from warnings plugin in multi-branch-pipeline project
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-39533 no graph displayed from warnings plugin in multi-branch-pipeline project Change By: Matthew DeTullio Component/s: workflow-multibranch-plugin Component/s: multi-branch-project-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-39533) no graph displayed from warnings plugin in multi-branch-pipeline project
Title: Message Title Matthew DeTullio assigned an issue to Ulli Hafner Jenkins / JENKINS-39533 no graph displayed from warnings plugin in multi-branch-pipeline project Change By: Matthew DeTullio Assignee: Matthew DeTullio Ulli Hafner Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39171) NPE when using properties from @Field in multibranch-pipeline
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-39171 NPE when using properties from @Field in multibranch-pipeline Change By: Matthew DeTullio Component/s: workflow-multibranch-plugin Component/s: multi-branch-project-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-39171) NPE when using properties from @Field in multibranch-pipeline
Title: Message Title Matthew DeTullio assigned an issue to Unassigned Jenkins / JENKINS-39171 NPE when using properties from @Field in multibranch-pipeline Change By: Matthew DeTullio Assignee: Matthew DeTullio Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39487) SVN changesets duplicated when using multibranch pipeline
Title: Message Title Matthew DeTullio assigned an issue to Unassigned Jenkins / JENKINS-39487 SVN changesets duplicated when using multibranch pipeline Change By: Matthew DeTullio Assignee: Matthew DeTullio Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39487) SVN changesets duplicated when using multibranch pipeline
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-39487 SVN changesets duplicated when using multibranch pipeline Change By: Matthew DeTullio Component/s: workflow-multibranch-plugin Component/s: multi-branch-project-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-39771) Failed to load org.jenkinsci.plugins.orgfolder.github.MainLogic
Title: Message Title Matthew DeTullio assigned an issue to Unassigned Jenkins / JENKINS-39771 Failed to load org.jenkinsci.plugins.orgfolder.github.MainLogic Change By: Matthew DeTullio Assignee: Matthew DeTullio Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39771) Failed to load org.jenkinsci.plugins.orgfolder.github.MainLogic
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-39771 Failed to load org.jenkinsci.plugins.orgfolder.github.MainLogic Change By: Matthew DeTullio Component/s: workflow-multibranch-plugin Component/s: multi-branch-project-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-39861) Jenkinsfile path of Multibranch pipeline
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-39861 Jenkinsfile path of Multibranch pipeline Change By: Matthew DeTullio Component/s: workflow-multibranch-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-39861) Jenkinsfile path of Multibranch pipeline
Title: Message Title Matthew DeTullio assigned an issue to Unassigned Jenkins / JENKINS-39861 Jenkinsfile path of Multibranch pipeline Change By: Matthew DeTullio Assignee: Matthew DeTullio Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39861) Jenkinsfile path of Multibranch pipeline
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-39861 Jenkinsfile path of Multibranch pipeline Change By: Matthew DeTullio Component/s: pipeline Component/s: workflow-multibranch-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-39861) Jenkinsfile path of Multibranch pipeline
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-39861 Jenkinsfile path of Multibranch pipeline Change By: Matthew DeTullio Component/s: workflow-multibranch-plugin Component/s: multi-branch-project-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-39650) Can not change branch job configurations when using Multibranch pipeline
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-39650 Can not change branch job configurations when using Multibranch pipeline Change By: Matthew DeTullio Component/s: workflow-multibranch-plugin Component/s: multi-branch-project-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-39650) Can not change branch job configurations when using Multibranch pipeline
Title: Message Title Matthew DeTullio assigned an issue to Unassigned Jenkins / JENKINS-39650 Can not change branch job configurations when using Multibranch pipeline Change By: Matthew DeTullio Assignee: Matthew DeTullio Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39981) REGRESSION empty multibranch projects are throwing exception
Title: Message Title Michael Neale resolved as Fixed Jenkins / JENKINS-39981 REGRESSION empty multibranch projects are throwing exception Change By: Michael Neale Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39979) REGRESSION Errors on branches tab when not supported
Title: Message Title Michael Neale updated JENKINS-39979 Jenkins / JENKINS-39979 REGRESSION Errors on branches tab when not supported Change By: Michael Neale 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-40027) REGRESSION: can't open branches that have / in the name (eg git flow)
Title: Message Title Michael Neale commented on JENKINS-40027 Re: REGRESSION: can't open branches that have / in the name (eg git flow) Hey Thorsten Scherler if you don't get to this on friday, could you give it to Ivan ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40027) REGRESSION: can't open branches that have / in the name (eg git flow)
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-40027
REGRESSION: can't open branches that have / in the name (eg git flow)
Change By:
Michael Neale
This is really bad. This is a terrible regression which there should have been ATH coverage (there is for folder paths). To reproduce: * Setup the github project: kzantow/failure project* Try to open feature/something branchTo fix: * Ad an ATH that actually tests this DONE by mic: https://github.com/jenkinsci/blueocean-acceptance-test/pull/72 * then fix itWill not open and will show up in log as: {noformat}http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/keitha/branches/feature/something/runs/1/ Failed to load resource: the server responded with a status of 404 (Not Found)blueocean.js:1491 Uncaught (in promise) Error: Not Found(…){noformat}\it should instead be loading the encoded form of the feature/something
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this
[JIRA] (JENKINS-40027) REGRESSION: can't open branches that have / in the name (eg git flow)
Title: Message Title Michael Neale commented on JENKINS-40027 Re: REGRESSION: can't open branches that have / in the name (eg git flow) I have ATH coverage for this in this PR: https://github.com/jenkinsci/blueocean-acceptance-test/pull/72 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40028) Missing license
Title: Message Title Fritz Elfert commented on JENKINS-40028 Re: Missing license Result: As of right now, 4 of the 5 other maintainers have agreed to choose ASL 2.0. I choose ASL 2.0 Marat Mavliutov has not responded so far. Therefore an absolute majority of the maintainers chose ASL 2.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40028) Missing license
Title: Message Title Fritz Elfert updated an issue Jenkins / JENKINS-40028 Missing license Change By: Fritz Elfert Attachment: response-adrian-cole.eml Attachment: response-andrew-bayer.eml Attachment: response-monty-taylor.eml Attachment: response-vijay-kiran.eml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. 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-40028) Missing license
Title: Message Title Fritz Elfert created an issue Jenkins / JENKINS-40028 Missing license Issue Type: Task Assignee: Fritz Elfert Components: jclouds-plugin Created: 2016/Nov/25 12:53 AM Priority: Major Reporter: Fritz Elfert The plugin has no license information anywhere. I have contacted the other maintainers via mail and asked for a decision. This issue exists in order to record their responses. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40027) REGRESSION: can't open branches that have / in the name (eg git flow)
Title: Message Title Michael Neale commented on JENKINS-40027 Re: REGRESSION: can't open branches that have / in the name (eg git flow) Cliff Meyers you will hate this one - I think the mobx changes hosed all the stuff to do with encoding 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-40027) REGRESSION: can't open branches that have / in the name (eg git flow)
Title: Message Title Michael Neale assigned an issue to Thorsten Scherler Jenkins / JENKINS-40027 REGRESSION: can't open branches that have / in the name (eg git flow) Change By: Michael Neale Assignee: Thorsten Scherler Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40027) REGRESSION: can't open branches that have / in the name (eg git flow)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40027 REGRESSION: can't open branches that have / in the name (eg git flow) Change By: Michael Neale Sprint: tasman Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40027) REGRESSION: can't open branches that have / in the name (eg git flow)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40027 REGRESSION: can't open branches that have / in the name (eg git flow) Change By: Michael Neale Summary: REGRESSION: can't open paths branches that have / in the name (eg git flow) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40027) REGRESSION: can't open paths that have / in the name (eg git flow)
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-40027
REGRESSION: can't open paths that have / in the name (eg git flow)
Change By:
Michael Neale
This is really bad. This is a terrible regression which there should have been ATH coverage (there is for folder paths). To reproduce: * Setup the github project: kzantow/failure project* Try to open feature/something branch To fix: * Ad an ATH that actually tests this * then fix it Will not open and will show up in log as: {noformat}http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/keitha/branches/feature/something/runs/1/ Failed to load resource: the server responded with a status of 404 (Not Found)blueocean.js:1491 Uncaught (in promise) Error: Not Found(…){noformat}\it should instead be loading the encoded form of the feature/something
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To
[JIRA] (JENKINS-40027) REGRESSION: can't open paths that have / in the name (eg git flow)
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-40027 REGRESSION: can't open paths that have / in the name (eg git flow) Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/25 12:22 AM Priority: Blocker Reporter: Michael Neale This is really bad. This is a terrible regression which there should have been ATH coverage (there is for folder paths). To reproduce: Setup the github project: kzantow/failure project Try to open feature/something branch Will not open and will show up in log as: http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/keitha/branches/feature/something/runs/1/ Failed to load resource: the server responded with a status of 404 (Not Found) blueocean.js:1491 Uncaught (in promise) Error: Not Found(…) \ it should instead be loading the encoded form of the feature/something
[JIRA] (JENKINS-39809) 404s pages are inconsistent - blank page, ugly 404 and flashy 404
Title: Message Title Michael Neale commented on JENKINS-39809 Re: 404s pages are inconsistent - blank page, ugly 404 and flashy 404 Can you make a follow on ticket? the case I saw that didn't work was pipeline results screen (is that what you mean?) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40026) Pipeline hides the cause of AbortException and make it harder to diagnose the root cause
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-40026 Pipeline hides the cause of AbortException and make it harder to diagnose the root cause Change By: Cyrille Le Clerc Summary: Pipeline hides the cause of AbortException and make it much harder to diagnose the root cause Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40026) Pipeline hides the cause of AbortException and make it much harder to diagnose the root cause
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-40026
Pipeline hides the cause of AbortException and make it much harder to diagnose the root cause
Change By:
Cyrille Le Clerc
When an AbortException is raised in a pipeline build, the console only display the String message of the AbortException (e.g. "ERROR: 'copyRemoteArtifacts' step could not complete") and does not display the stack trace that would help greatly to understand the cause.I had to wrap my failing step in "try {}catch(){}" to discover the root cause.I got " a generic message that does not explain the cause :{noformat} ERROR: 'copyRemoteArtifacts' step could not complete " that does not explain {noformat}When the cause when the root exception displayed by "try {}catch(){}" was clear:{noformat}hudson.AbortException: 'copyRemoteArtifacts' step could not complete at com.cloudbees.opscenter.artifacts.RemoteArtifactCopyStepExecution.abort(RemoteArtifactCopyStepExecution.java:159) at com.cloudbees.opscenter.artifacts.RemoteArtifactCopyStepExecution.run(RemoteArtifactCopyStepExecution.java:108) at com.cloudbees.opscenter.artifacts.RemoteArtifactCopyStepExecution.run(RemoteArtifactCopyStepExecution.java:34) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 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.util.concurrent.ExecutionException: java.io.IOException: Source job does not exist or you do not have permission to see the source job at com.cloudbees.opscenter.context.rpc.RPCFuture.get(RPCFuture.java:272) at com.cloudbees.opscenter.artifacts.RemoteArtifactCopyCallable.invoke(RemoteArtifactCopyCallable.java:237) at com.cloudbees.opscenter.artifacts.RemoteArtifactCopyCallable.invoke(RemoteArtifactCopyCallable.java:174) at com.cloudbees.opscenter.artifacts.RemoteArtifactCopyStepExecution.run(RemoteArtifactCopyStepExecution.java:103) ... 9 moreCaused by: java.io.IOException: Source job does not exist or you do not have permission to see the source job at com.cloudbees.opscenter.artifacts.RemoteArtifactCopyCallable.call(RemoteArtifactCopyCallable.java:447) at com.cloudbees.opscenter.artifacts.RemoteArtifactCopyCallable.call(RemoteArtifactCopyCallable.java:59) at com.cloudbees.opscenter.context.remote.RemoteAuthentication.impersonate(RemoteAuthentication.java:88) at com.cloudbees.opscenter.context.rpc.RPCRequest$1.call(RPCRequest.java:217) at hudson.remoting.LocalChannel$1.call(LocalChannel.java:52)
[JIRA] (JENKINS-40026) Pipeline hides the cause of AbortException and make it much harder to diagnose the root cause
Title: Message Title
Cyrille Le Clerc created an issue
Jenkins / JENKINS-40026
Pipeline hides the cause of AbortException and make it much harder to diagnose the root cause
Issue Type:
Improvement
Assignee:
Unassigned
Components:
pipeline
Created:
2016/Nov/24 11:48 PM
Environment:
Jenkins ver. 2.7.21.1 Pipeline 2.4
Priority:
Minor
Reporter:
Cyrille Le Clerc
When an AbortException is raised in a pipeline build, the console only display the String message of the AbortException (e.g. "ERROR: 'copyRemoteArtifacts' step could not complete") and does not display the stack trace that would help greatly to understand the cause. I had to wrap my failing step in "try {}catch(){}" to discover the root cause. I got "ERROR: 'copyRemoteArtifacts' step could not complete" that does not explain the cause when the root exception was clear:
hudson.AbortException: 'copyRemoteArtifacts' step could not complete
at com.cloudbees.opscenter.artifacts.RemoteArtifactCopyStepExecution.abort(RemoteArtifactCopyStepExecution.java:159)
at com.cloudbees.opscenter.artifacts.RemoteArtifactCopyStepExecution.run(RemoteArtifactCopyStepExecution.java:108)
at com.cloudbees.opscenter.artifacts.RemoteArtifactCopyStepExecution.run(RemoteArtifactCopyStepExecution.java:34)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52)
at hudson.security.ACL.impersonate(ACL.java:213)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49)
at
[JIRA] (JENKINS-40025) Conflict active-choices-plugin with jquery-plugin
Title: Message Title
Yuriy Burtsev updated an issue
Jenkins / JENKINS-40025
Conflict active-choices-plugin with jquery-plugin
Change By:
Yuriy Burtsev
active-choices-plugin with jquery-plugin (which needed for sonar plugin) does not update data in Active Choices Reactive Parameter.Example Jenkinsfile:{code:java}properties([parameters([booleanParam(defaultValue: false, description: '', name: 'RELEASE'), [$class: 'CascadeChoiceParameter', choiceType: 'PT_SINGLE_SELECT', description: '', filterable: false, name: 'TEST', randomName: 'choice-parameter-123', referencedParameters: 'RELEASE', script: [$class: 'GroovyScript', fallbackScript: [classpath: [], sandbox: false, script: ''], script: [classpath: [], sandbox: false, script: '''if (RELEASE.equals(\'on\')){return ['xtrue',RELEASE] }else{return ['xfalse',RELEASE]}'''), pipelineTriggers([])]){code} After remove jquery-plugin all work perfect.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because
[JIRA] (JENKINS-40025) Conflict active-choices-plugin with jquery-plugin
Title: Message Title
Yuriy Burtsev updated an issue
Jenkins / JENKINS-40025
Conflict active-choices-plugin with jquery-plugin
Change By:
Yuriy Burtsev
active-choices-plugin with jquery-plugin does not update data in Active Choices Reactive Parameter.Example Jenkinsfile: {code:java} properties([parameters([booleanParam(defaultValue: false, description: '', name: 'RELEASE'), [$class: 'CascadeChoiceParameter', choiceType: 'PT_SINGLE_SELECT', description: '', filterable: false, name: 'TEST', randomName: 'choice-parameter-123', referencedParameters: 'RELEASE', script: [$class: 'GroovyScript', fallbackScript: [classpath: [], sandbox: false, script: ''], script: [classpath: [], sandbox: false, script: '''if (RELEASE.equals(\'on\')){return ['xtrue',RELEASE] }else{return ['xfalse',RELEASE]}'''), pipelineTriggers([])]) {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
[JIRA] (JENKINS-40025) Conflict active-choices-plugin with jquery-plugin
Title: Message Title
Yuriy Burtsev created an issue
Jenkins / JENKINS-40025
Conflict active-choices-plugin with jquery-plugin
Issue Type:
Bug
Assignee:
Bruno P. Kinoshita
Components:
active-choices-plugin, jquery-plugin, sonar
Created:
2016/Nov/24 11:13 PM
Environment:
Jenkins 2.19.3 active-choices-plugin 1.5.2 jquery plugin 1.11.2-0 sonar plugin 2.5
Labels:
plugin plugins
Priority:
Critical
Reporter:
Yuriy Burtsev
active-choices-plugin with jquery-plugin does not update data in Active Choices Reactive Parameter. Example Jenkinsfile: properties([parameters([booleanParam(defaultValue: false, description: '', name: 'RELEASE'), [$class: 'CascadeChoiceParameter', choiceType: 'PT_SINGLE_SELECT', description: '', filterable: false, name: 'TEST', randomName: 'choice-parameter-123', referencedParameters: 'RELEASE', script: [$class: 'GroovyScript', fallbackScript: [classpath: [], sandbox: false, script: ''], script: [classpath: [], sandbox: false, script: ''' if (RELEASE.equals(\'on\')) { return ['xtrue',RELEASE] } else { return ['xfalse',RELEASE] } '''), pipelineTriggers([])])
[JIRA] (JENKINS-37295) Redesign the empty states
Title: Message Title Brody Maclean updated JENKINS-37295 Jenkins / JENKINS-37295 Redesign the empty states Change By: Brody Maclean 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-39892) When the run fails with tests or another analysis then it should be more obvious
Title: Message Title Brody Maclean started work on JENKINS-39892 Change By: Brody Maclean 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-39891) Add i18n backend into a plugin and distribute with Blue Ocean
Title: Message Title Michael Neale commented on JENKINS-39891 Re: Add i18n backend into a plugin and distribute with Blue Ocean FYI when it is time to publish, github.com/jenkins-infra/repository-permissions-updater will need a PR to give permissions to push the new hpi 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-39993) Scrolling changes only shows 1 line even if there are lots of stages wrapped across multiple lines
Title: Message Title Geoff Dunn commented on JENKINS-39993 Re: Scrolling changes only shows 1 line even if there are lots of stages wrapped across multiple lines I don't really need an option. Just use the full vertical height of the cell. It gets cut back to 1-2 lines when in many cases there is 4-5 lines there. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39993) Scrolling changes only shows 1 line even if there are lots of stages wrapped across multiple lines
Title: Message Title Geoff Dunn commented on JENKINS-39993 Re: Scrolling changes only shows 1 line even if there are lots of stages wrapped across multiple lines I've attached some screenshot examples of before and after. Unfortunately I have to heavily blur them to hide any commercially sensitive information. But you should still get the idea of how I'm using the view Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39993) Scrolling changes only shows 1 line even if there are lots of stages wrapped across multiple lines
Title: Message Title Geoff Dunn updated an issue Jenkins / JENKINS-39993 Scrolling changes only shows 1 line even if there are lots of stages wrapped across multiple lines Change By: Geoff Dunn Attachment: 1.1 example.png Attachment: 1.2 example1.png Attachment: 1.2 example2.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-40024) Cannot use another job as a template
Title: Message Title Dominik Brulińsi created an issue Jenkins / JENKINS-40024 Cannot use another job as a template Issue Type: Bug Assignee: Joel Johnson Components: ez-templates-plugin Created: 2016/Nov/24 8:20 PM Priority: Major Reporter: Dominik Brulińsi I find an idea of EZ Templates Plugin very useful. Unfortunately I cannot make it work. I tested steps bellow on our jenkins 1.626 and fresh install of 2.19.3. 1. Create "Freestyle Project" let's call it "test". 2. Check "Allow this job to be used as a template" in configuration" 3. Add build step for example "Execute shell" with command "ls" 4. Save configuration -- EFFECT: job is created and checkbox "Allow this job to be used as a template" is still checked. Every thing is fine for now. 5. Create project for example "test2" 6. Add build step for example "Execute shell" with command "pwd" 7. Save configuration -- EFFECT: job is created and looks fine 8. Edit "test2" and check "Use another job as a template". 9. Select "test". 10. Save configuration. -- EFFECT: job is exactly the same as after step 7. In configuration checkbox "Use another job as a template" is unchecked. Am I doing something wrong? Have you encountered similar problem?
[JIRA] (JENKINS-39989) Core-js had(s) broken lint and tests - should be run as part of pipeline
Title: Message Title Thorsten Scherler updated JENKINS-39989 Jenkins / JENKINS-39989 Core-js had(s) broken lint and tests - should be run as part of pipeline Change By: Thorsten Scherler 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-39499) There is no way to set changeSet property of shared library checkout to false
Title: Message Title
Kenneth Brooks edited a comment on JENKINS-39499
Re: There is no way to set changeSet property of shared library checkout to false
Same issue for us.We have lots of multibranch builds all using a global shared library that we are building.Every change for the library shows up in the changeset of the target app build.Also, the status of the target app build shows up against the commits of the global libraries in bitbucket. I agree with the OP suggestion of defaulting the changeset to false. Perhaps with the ability to override globally in the configs. I haven't pulled the code but I believe it is this line: https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/libs/SCMSourceRetriever.java#L90{code:java}delegate.setChangelog(true); // TODO is this desirable?{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-40023) JGit changelog list no changes prior to merge commit
Title: Message Title
tzafrir created an issue
Jenkins / JENKINS-40023
JGit changelog list no changes prior to merge commit
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-client-plugin
Created:
2016/Nov/24 7:23 PM
Priority:
Minor
Reporter:
tzafrir
git-client version 2.1.0 Adding the below test case in GitAPITestCase.java fails with JGit but passes with CliGit. For JGit it seems that after RevWalker check the merge commit at HEAD, it finds no prior commits to list and show in the changelog. Whereas the CliGit does find the commit with the message "commit1" and returns it's SHA1
public void test_changelog_with_merge_commit() throws Exception {
w.init();
w.commitEmpty("init");
// First commit to branch1
w.git.branch("branch1");
w.git.checkout("branch1");
w.touch("file1", "content1");
w.git.add("file1");
w.git.commit("commit1");
String commitSha1 = w.git.revParse("HEAD").name();
// Merge branch1 into master
w.git.checkout("master");
String mergeMessage = "Merge message to be tested.";
w.git.merge().setMessage(mergeMessage).setGitPluginFastForwardMode(MergeCommand.GitPluginFastForwardMode.NO_FF).setRevisionToMerge(w.git.getHeadRev(w.repoPath(), "branch1")).execute();
// Obtain last commit message
String mergeSha1 = w.git.revParse("HEAD").name();
check_changelog_sha1(commitSha1, "master");
}
[JIRA] (JENKINS-39499) There is no way to set changeSet property of shared library checkout to false
Title: Message Title Kenneth Brooks commented on JENKINS-39499 Re: There is no way to set changeSet property of shared library checkout to false Same issue for us. We have lots of multibranch builds all using a global shared library that we are building. Every change for the library shows up in the changeset of the target app build. Also, the status of the target app build shows up against the commits of the global libraries in bitbucket. I agree with the OP suggestion of defaulting the changeset to false. Perhaps with the ability to override globally in the configs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39832) org.eclipse.jgit.errors.MissingObjectException: Missing commi
Title: Message Title James Dumay commented on JENKINS-39832 Re: org.eclipse.jgit.errors.MissingObjectException: Missing commi Good to know - thanks mate! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40018) Restrict target URL scope
Title: Message Title Goran Sarenkapa commented on JENKINS-40018 Re: Restrict target URL scope I don't understand what you mean, can you elaborate. ZAP 2.5.X requires a starting point URL to be provided, this is from where the scan will originate as described in the documentation and the help tip in the plugin itself. It is not possible to leave this field empty. Similarly i am not sure how you would set this up in the UI either since it's not an available functionality. You can include regex already into the context for each specific build. But i also don't understand why this should be in the administration interface as a global setting rather than on a per job basis and specific to each application under test. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40021) Cannot skip admin parameter in job creation
Title: Message Title Goran Sarenkapa commented on JENKINS-40021 Re: Cannot skip admin parameter in job creation Changed from Major Bug to Minor Improvement since it is functioning currently as intended. May change in future to use a checkbox to signify if an override should be applied or not. Currently tho Override Host: Override Port: The value has to be provided, regardless if it's overridden or not. The purpose of the admin config is to pre-populate those text boxes but that requires one save action of the admin config page. If you have any questions please feel free to ask and i will try to clarify. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40021) Cannot skip admin parameter in job creation
Title: Message Title Goran Sarenkapa updated an issue Jenkins / JENKINS-40021 Cannot skip admin parameter in job creation Change By: Goran Sarenkapa Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40021) Cannot skip admin parameter in job creation
Title: Message Title Goran Sarenkapa updated an issue Jenkins / JENKINS-40021 Cannot skip admin parameter in job creation Change By: Goran Sarenkapa Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39695) Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error
Title: Message Title Carlos Sanchez commented on JENKINS-39695 Re: Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error the resolution should happen in the jenkins agent, the jnlp continer inside the pod Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39862) Make stash/unstash work in container.inside
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39862 Make stash/unstash work in container.inside Change By: Julien Pivotto Summary: Make stash/unstash work in containter container .inside Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40020) Failing to start Jenkins. No JSP support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
Title: Message Title Naveen Kumar resolved as Fixed Updating Java to 1.8 helped fixing this issue. Jenkins / JENKINS-40020 Failing to start Jenkins. No JSP support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet Change By: Naveen Kumar 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
[JIRA] (JENKINS-40022) Unable to add Deploy Maven artifacts step via DSL
Title: Message Title Jakub Bochenski created an issue Jenkins / JENKINS-40022 Unable to add Deploy Maven artifacts step via DSL Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2016/Nov/24 5:06 PM Priority: Critical Reporter: Jakub Bochenski Tried No signature of method: javaposse.jobdsl.dsl.helpers.step.StepContext.deployArtifacts() is applicable for argument types: () values: [] and No signature of method: javaposse.jobdsl.dsl.helpers.step.StepContext.redeployPublisher() is applicable for argument types: and No signature of method: javaposse.jobdsl.dsl.helpers.step.StepContext.redeployBatchTaskPublisher() is applicable for argument types: to no avail
[JIRA] (JENKINS-40021) Cannot skip admin parameter in job creation
Title: Message Title Goran Sarenkapa commented on JENKINS-40021 Re: Cannot skip admin parameter in job creation Not a bug, depends on your Jenkins version. You need to go to admin configurations and press save once. Then the textboxes should be populated. The value is still required in the actual textbox, whether it's an override 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-40021) Cannot skip admin parameter in job creation
Title: Message Title Goran Sarenkapa updated an issue Jenkins / JENKINS-40021 Cannot skip admin parameter in job creation Change By: Goran Sarenkapa Labels: bug zap-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-40021) Cannot skip admin parameter in job creation
Title: Message Title Goran Sarenkapa edited a comment on JENKINS-40021 Re: Cannot skip admin parameter in job creation Not a bug, depends on your Jenkins version. You need to go to admin configurations and press save once. Then the textboxes should be populated in the job's configuration . The value is still required in the actual textbox, whether it's an override 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-40021) Cannot skip admin parameter in job creation
Title: Message Title Guillaume L created an issue Jenkins / JENKINS-40021 Cannot skip admin parameter in job creation Issue Type: Bug Assignee: Goran Sarenkapa Components: zap-plugin Created: 2016/Nov/24 4:54 PM Priority: Major Reporter: Guillaume L When trying to create a job with a zap scan, Override Host and Override Port are marked as Mandatory in the Admin Configurations section although they are defined in the Jenkins Admin configuration. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-40020) Failing to start Jenkins. No JSP support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
Title: Message Title
Naveen Kumar created an issue
Jenkins / JENKINS-40020
Failing to start Jenkins. No JSP support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
jenkins.log
Components:
winstone-jetty
Created:
2016/Nov/24 4:47 PM
Environment:
Linux localhost.localdomain 3.10.0-123.el7.x86_64 #1 SMP Mon Jun 30 12:09:22 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux java version "1.7.0_111" OpenJDK Runtime Environment (rhel-2.6.7.2.el7_2-x86_64 u111-b01) OpenJDK 64-Bit Server VM (build 24.111-b01, mixed mode) Jenkins version: jenkins-2.33-1.1.noarch.rpm
Labels:
jenkins
Priority:
Critical
Reporter:
Naveen Kumar
I am trying to install Jenkins in Centos. Starting of jenkins fails with the below errors on console: [root@localhost ~]# java -DJENKINS_HOME=/root/.jenkins -jar /usr/lib/jenkins/jenkins.war --httpPort=8082 Running from: /usr/lib/jenkins/jenkins.war webroot: System.getProperty("JENKINS_HOME") Nov 24, 2016 4:05:28 AM Main deleteWinstoneTempContents WARNING: Failed to delete the temporary Winstone file /tmp/winstone/jenkins.war Nov 24, 2016 4:05:28 AM org.eclipse.jetty.util.log.JavaUtilLog info INFO: Logging initialized @318ms Nov 24, 2016 4:05:28 AM winstone.Logger logInternal INFO: Beginning extraction from war file Nov 24, 2016 4:05:30 AM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING:
[JIRA] (JENKINS-40008) Changesets are not displayed when special chars in project name
Title: Message Title Mathieu CABARET commented on JENKINS-40008 Re: Changesets are not displayed when special chars in project name I've pipeline-stage-view@2.3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39964) jenkins/user/username/configure throws No page found
Title: Message Title Lars Urban commented on JENKINS-39964 Re: jenkins/user/username/configure throws No page found The same for me, fresh install Today =/ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40008) Changesets are not displayed when special chars in project name
Title: Message Title Paul Horvath edited a comment on JENKINS-40008 Re: Changesets are not displayed when special chars in project name I should remove that but removed it complicates debugging from the code 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-40008) Changesets are not displayed when special chars in project name
Title: Message Title Paul Horvath updated an issue Jenkins / JENKINS-40008 Changesets are not displayed when special chars in project name Change By: Paul Horvath Comment: what version of https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin you have? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40008) Changesets are not displayed when special chars in project name
Title: Message Title Paul Horvath commented on JENKINS-40008 Re: Changesets are not displayed when special chars in project name I should remove that but it complicates debugging Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40008) Changesets are not displayed when special chars in project name
Title: Message Title Paul Horvath commented on JENKINS-40008 Re: Changesets are not displayed when special chars in project name what version of https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin you have? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38523) Stage listing flashes "no steps" when loading a stage for the first time
Title: Message Title Thorsten Scherler stopped work on JENKINS-38523 Change By: Thorsten Scherler 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-39229) Regression: Initial stage run does not show graph
Title: Message Title Thorsten Scherler started work on JENKINS-39229 Change By: Thorsten Scherler 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-40011) Deploy artifacts to Maven repository ignores Global MAVEN_OPTS
Title: Message Title Jakub Bochenski commented on JENKINS-40011 Re: Deploy artifacts to Maven repository ignores Global MAVEN_OPTS Deploy works fine when using user/password authentication: Maven RedeployPublisher use remote IQ-449a33ad36b4 maven settings from : /tmp/settings5578981742753340929.xml [INFO] Deployment in https://mvnrepo.acme-it.com/content/repositories/snapshots/ (id=nexus,uniqueVersion=true) Deploying the main artifact aggregator-29.3.0-SNAPSHOT.pom Downloading: https://mvnrepo.acme-it.com/content/repositories/snapshots/com/purato/aggregator/29.3.0-SNAPSHOT/maven-metadata.xml Downloaded: https://mvnrepo.acme-it.com/content/repositories/snapshots/com/purato/aggregator/29.3.0-SNAPSHOT/maven-metadata.xml (601 B at 1.9 KB/sec) Uploading: https://mvnrepo.acme-it.com/content/repositories/snapshots/com/purato/aggregator/29.3.0-SNAPSHOT/aggregator-29.3.0-20161124.155824-18.pom Uploaded: https://mvnrepo.acme-it.com/content/repositories/snapshots/com/purato/aggregator/29.3.0-SNAPSHOT/aggregator-29.3.0-20161124.155824-18.pom (8 KB at 86.0 KB/sec) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you 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-39229) Regression: Initial stage run does not show graph
Title: Message Title Thorsten Scherler assigned an issue to Thorsten Scherler Jenkins / JENKINS-39229 Regression: Initial stage run does not show graph Change By: Thorsten Scherler Assignee: Tom FENNELLY Thorsten Scherler Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40019) slave containers are not cleaned up.
Title: Message Title Andrew Greenwood created an issue Jenkins / JENKINS-40019 slave containers are not cleaned up. Issue Type: Bug Assignee: Nicolas De Loof Components: docker-slaves-plugin Created: 2016/Nov/24 3:54 PM Environment: Jenkins 2.27 docker-slaves-plugin 1.0.5 Priority: Minor Reporter: Andrew Greenwood The main slave containers are not removed after job completes... # docker ps -a CONTAINER IDIMAGE COMMAND CREATED STATUS PORTS NAMES 61c83a8fd3e2jenkinsci/slave "java -Djava.io.tmpdi" 9 minutes ago Exited (0) 9 minutes ago thirsty_ardinghelli ffee427d5c00jenkinsci/slave "java -Djava.io.tmpdi" 9 minutes ago Exited (0) 9 minutes ago distracted_perlman b25cef18c35fjenkinsci/slave "java -Djava.io.tmpdi" 10 minutes ago Exited (0) 9 minutes ago nostalgic_meninsky 2116b508126bjenkinsci/slave "java -Djava.io.tmpdi" 19 hours agoExited (0) 19 hours ago happy_leakey bccec6db5efdjenkinsci/slave "java -Djava.io.tmpdi" 19 hours agoExited (0) 19 hours ago tender_ramanujan c52ea168536djenkinsci/slave "java -Djava.io.tmpdi" 23 hours agoExited (143) 1 seconds ago berserk_knuth fbf52b0bc679jenkinsci/slave "java -Djava.io.tmpdi" 23 hours agoExited (0) 23 hours ago determined_cori ee3b6b237803
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Roman Karlstetter commented on JENKINS-38860 Re: Git plugin using local config to update submodules In my experience, running git submodule deinit . (for example as a pre-scm-build-step) does not work. What works for me: remove advanced submodule behavior git submodule deinit . as pre-scm build-step (this is optional, might not be necessary) git submodule update --init as first build step after checkout Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
