[JIRA] (JENKINS-38679) Workspace doesn't contain https://svn/global-library-repo${library.myib.version}. Need a new build.
Title: Message Title Anton Lundin created an issue Jenkins / JENKINS-38679 Workspace doesn't contain https://svn/global-library-repo${library.myib.version}. Need a new build. Issue Type: Bug Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2016/Oct/04 6:56 AM Priority: Minor Reporter: Anton Lundin I see a wierd bug when using global libraries on pipeline. Every poll scm poll call finishes like: Workspace doesn't contain https://svn/global-library-repo$ {library.mylib.version} . Need a new build. Everything loads just file when i use: @Library("mylib@/trunk") import mylib but the polling bug makes it re-build every poll call. I use the Legacy SCM api to declare the lib, because the modern scm dropdown is empty. Add Comment
[JIRA] (JENKINS-38656) Can't build with JDK 1.6
Title: Message Title Andrea Mariottini updated an issue Jenkins / JENKINS-38656 Can't build with JDK 1.6 Change By: Andrea Mariottini Summary: Can' t build with JDK 1.6 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38192) workspace isn't reused between builds
Title: Message Title Nicolas De Loof closed an issue as Fixed Jenkins / JENKINS-38192 workspace isn't reused between builds Change By: Nicolas De Loof 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-38265) incorrect PATH set on build environment
Title: Message Title Nicolas De Loof resolved as Fixed Jenkins / JENKINS-38265 incorrect PATH set on build environment Change By: Nicolas De Loof 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-26757) "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs
Title: Message Title Kiran Anugurthi closed an issue as Fixed Jenkins / JENKINS-26757 "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs Change By: Kiran Anugurthi 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-38442) Support nested stages in the Pipeline Graph
Title: Message Title Michael Neale commented on JENKINS-38442 Re: Support nested stages in the Pipeline Graph Kaden Wilkinson good to know. Yes showing something meaningful certainly should happen no matter what. Labelling is also very nice. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38592) pipelines data for json is getting a bit too crazy (for dashboard)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38592 pipelines data for json is getting a bit too crazy (for dashboard) Change By: Michael Neale Summary: pipelines data for json is getting a bit too crazy (for dashboard) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38592) pipelines data for json is getting a bit too crazy
Title: Message Title Michael Neale commented on JENKINS-38592 Re: pipelines data for json is getting a bit too crazy One point Vivek and I discussed: do we need the latest run of each pipeline to return everything? or could it be a summary of what we known is needed on the screen? when a pipeline detail is loaded then we do a full fetch anyway right Cliff Meyers Thorsten Scherler? Vivek also thinks making use of the tree api could be a better bet (ie only request what we know is needed). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38678) If the JNLP port is changed to a port in use and then changed to a port not in use, a stack trace appears
Title: Message Title Vincent Latombe started work on JENKINS-38678 Change By: Vincent Latombe 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-38677) Failure to create label in TFS
Title: Message Title Andrew Gray created an issue Jenkins / JENKINS-38677 Failure to create label in TFS Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 2016/Oct/04 5:22 AM Environment: Windows 2012 Jenkins 2.24 tfs-plugin 5.2.1 Labels: tfs-plugin Priority: Critical Reporter: Andrew Gray Since upgrading to 5.2.1 of the TFS plugin bad things have started happening: Last step is to apply label to TFS if all unit tests pass. Instead I get this more often than not: Creating label 'TPS_1927' on '$/PSD Team/TPS/TPS App' as of the current version in workspace 'Hudson-TPS-MASTER'... ERROR: Build step failed with exception java.lang.RuntimeException: java.lang.RuntimeException: Label creation failed. at hudson.plugins.tfs.model.Server.execute(Server.java:226) at hudson.plugins.tfs.TFSLabeler.perform(TFSLabeler.java:86) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Caused by: java.lang.RuntimeException: Label creation failed. at hudson.plugins.tfs.commands.LabelCommand.call(LabelCommand.java:70) at
[JIRA] (JENKINS-38678) If the JNLP port is changed to a port in use and then changed to a port not in use, a stack trace appears
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-38678 If the JNLP port is changed to a port in use and then changed to a port not in use, a stack trace appears Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Oct/04 5:22 AM Priority: Major Reporter: Vincent Latombe If a user changes the JNLP Port to a port in use and back to another port, the user is presented with a stack trace and cannot proceed. javax.servlet.ServletException: java.lang.UnsupportedOperationException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at com.cloudbees.jenkins.ha.HAHealthCheckFilter.doFilter(HAHealthCheckFilter.java:35) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:38) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter._doFilter(OfflineSecurityRealmFilter.java:90) at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter.doFilter(OfflineSecurityRealmFilter.java:67) at hudson.ut
[JIRA] (JENKINS-38678) If the JNLP port is changed to a port in use and then changed to a port not in use, a stack trace appears
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-38678 If the JNLP port is changed to a port in use and then changed to a port not in use, a stack trace appears Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38676) git summary should show the repository URL
Title: Message Title Jacob Keller created an issue Jenkins / JENKINS-38676 git summary should show the repository URL Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2016/Oct/04 5:20 AM Priority: Minor Reporter: Jacob Keller When using multiple git repositories in a pipeline, the git plugin adds a sumary for each built repository that looks something like Revision: a branch another branch ... another branch (Usually only one branch, but some cases show more). This summary could benefit from adding the repository URL or a human readable name, so that users can quickly see which revision belongs to what repository. Especially true when there are multiple repositories in a single build. Add Comment
[JIRA] (JENKINS-38675) gerrit trigger git summary show refspec instead of branch
Title: Message Title Jacob Keller created an issue Jenkins / JENKINS-38675 gerrit trigger git summary show refspec instead of branch Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger-plugin, git-client-plugin, git-plugin Created: 2016/Oct/04 5:18 AM Priority: Minor Reporter: Jacob Keller When you have multiple git projects in a pipeline build, multiple git summary bits appear in the build information when you highlight the build. These currently show something like Revision: a built branch another built branch When using the gerrit trigger plugin, the "built branches" only show the name of the branch from $GERRIT_BRANCH, instead of showing a refspec. Ideally when using these together, we should see the refspec instead of the branch because this is really what was built by the job. Add Comment
[JIRA] (JENKINS-38592) pipelines data for json is getting a bit too crazy
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38592 pipelines data for json is getting a bit too crazy Change By: Michael Neale In many cases the piplines json for the dashboard (search results) is blowing out to 14kb for 26 "rows" of data. This isn't a huge json transfer, but when you look closer, the impact of plugins adding to actions appears to be huge, and may be the cause of some problems. As part of looking at a support ticket [~tscherler] uncovered that for 26 pipelines, there is really 20 lines of attributes that are used by the dashboard == 520 lines (roughly). However there is 10k lines in the response - this is a bit out of control. It seems that every plugin installed adds actions for every little thing, which the dashboard doesn't need. For example{noformat}"_class": "io.jenkins.blueocean.service.embedded.rest.ActionProxiesImpl","_links": { "self": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/blue/rest/organizations/jenkins/... (hidden)" }},"_class": "com.cloudbees.plugins.credentials.ViewCredentialsAction","stores": {},"urlName": "credentials" }],{noformat}is added to every pipeline (along with 100's of others). Note also the whitespace (may be another problem). It really depends on the plugins. Also {noformat} {"_class": "hudson.model.TextParameterDefinition","defaultParameterValue": { "_class": "hudson.model.StringParameterValue", "name": "jiraComment", "value": ""},"description": "Additional info for theissue's comment","name": "jiraComment","type": "TextParameterDefinition" },{noformat}will never be of use to the dashboard (well probably). Some questions: Is there a better query to use to make the response smaller/more compact? (even just eyeballing the reponse could be helped by not returning the metadata optionally). I expect the calculation of this is quite expensive. Could this be a source of the slowdown when people have enough/certain plugins installed? Add Comment
[JIRA] (JENKINS-36823) Upgrade AWS SDK to 1.11.16 to enable ecs-plugin to use Task Roles
Title: Message Title Brian Holt commented on JENKINS-36823 Re: Upgrade AWS SDK to 1.11.16 to enable ecs-plugin to use Task Roles I was waiting on the AWS SDK plugin to be released, and it looks like there was finally a release a couple weeks ago. We've been using a local fork with this functionality since my original pull request was made back in August, so I'll prepare a pull request with the task role functionality sometime this week. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38506) Invalid workspace path for pipeline jobs on jenkins master
Title: Message Title Nick Archibald commented on JENKINS-38506 Re: Invalid workspace path for pipeline jobs on jenkins master Thanks Mike. The 'ws' command has "worked around" the problem for the time being. Obviously this needs to be corrected. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38601) Cannot mark Multibranch Pipeline as Favorite in Blue Ocean
Title: Message Title Michael Neale commented on JENKINS-38601 Re: Cannot mark Multibranch Pipeline as Favorite in Blue Ocean Thanks Kseniia Nenasheva - well spotted. Currently if you favourite it from blue ocean it should search for a suitable branch (but it won't look for the default as setup in github/bitbucket, as that information isn't currently available yet). However, from your steps, it looks like favouriting it from Jenkins itself is a problem? (this may be a related bug, but not quite the same). Blue ocean can only show favourites for a branch (hence it tries to pick a default) - it can't show a favourite of what is effectively a folder. The logic should be (for blue ocean): Favourite a MB pipeline -> choose default branch as per SCM provider -> (if none available) look for master/production/default named branch -> (if none found) -> pick the first one alphabetically so there is at least one branch. What I am curious about is what is the behavior if people don't want a favourite on a branch (I need to investigate that a bit) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38579) "All" view hyperlinks get localized, conflict with BlueOcean
Title: Message Title Michael Neale closed an issue as Duplicate Jenkins / JENKINS-38579 "All" view hyperlinks get localized, conflict with BlueOcean Change By: Michael Neale Status: Open Closed 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-38579) "All" view hyperlinks get localized, conflict with BlueOcean
Title: Message Title Michael Neale commented on JENKINS-38579 Re: "All" view hyperlinks get localized, conflict with BlueOcean Thanks Kseniia Nenasheva - I have linked this as a dupe of another ticket. This link should not be hard coded in blue ocean (there is some work under way for i18n) but also, this link shouldn't need to exist in the header once the create-pipeline features are there. so if it is ok, I will close this (and just link to it for the details). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36610) [Blue Ocean] Remove hard coded link to new job from blue ocean header
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36610 [Blue Ocean] Remove hard coded link to new job from blue ocean header Change By: Michael Neale Summary: const newJobUrl = `${baseUrl}/view/All/newJob` in PIpelines.jsx is hard coded and doesn't take into account localised URIs in jenkins. This should not be hard coded. This link should actually be removed from blue ocean header in longer term as it gets its own creation screen and doesn't have to delegate to classic. Fresh install of jenkins on my osx laptop.Installing plugin via experimental repository, everyting's ok.- *Jenkins* : http://localhost:7070/- *Blue Ocean* : http://localhost:7070/blue/ then automatic redirect to http://localhost:7070/blue/pipelines- *Click on "new pipeline"* : http://localhost:7070/view/All/newJob --> 404Opened an issue [https://groups.google.com/forum/#!topic/jenkinsci-dev/C7Ze59o_XOo] and guys redirected me to you. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You
[JIRA] (JENKINS-36610) [Blue Ocean] Remove hard coded link to new job from blue ocean header
Title: Message Title Michael Neale commented on JENKINS-36610 Re: [Blue Ocean] Remove hard coded link to new job from blue ocean header Thanks Maelig Gohin we want to get rid of this link in hard coded form anyway, so this should naturally go away. Will keep it open for now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36610) [Blue Ocean] Remove hard coded link to new job from blue ocean header
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36610 [Blue Ocean] Remove hard coded link to new job from blue ocean header Change By: Michael Neale Summary: [Blue Ocean] New pipeline --> 404 Remove hard coded link to new job from blue ocean header Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35845) Internationalisation for Blue Ocean and JDL
Title: Message Title Michael Neale commented on JENKINS-35845 Re: Internationalisation for Blue Ocean and JDL Keith Zantow - you were taking a look at this? Thorsten Scherler might want to check with keith before opening a PR (if work hasn't started). Also Keith - should route localisation be part of the scope of this? (do we want to do that? ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35845) Internationalisation for Blue Ocean and JDL
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35845 Internationalisation for Blue Ocean and JDL Change By: Michael Neale In Scope* All strings and formatting should be localisable* Short explanation on how we localise components and the app put in a README.md* Go through and extract all our current strings * Clarify if routes (URIs) should be localised as well (they can be in some jenkins URIs but not sure if that is by accident or by design). Notes* Looks like [react-intl|https://www.npmjs.com/package/react-intl] is the way things are done in React apps today. Here's a video from [React.js conf 2015|https://www.youtube.com/watch?v=Sla-DkvmIHY] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups
[JIRA] (JENKINS-38674) GitHubCommitStatusSetter unusable in pipeline with multiple checkout steps
Title: Message Title Logan Glickfield created an issue Jenkins / JENKINS-38674 GitHubCommitStatusSetter unusable in pipeline with multiple checkout steps Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2016/Oct/04 2:51 AM Priority: Major Reporter: Logan Glickfield We're using the Shared Libraries Plugin with our Jenkins Pipeline along with a checkout step. Combined this means there are two separate checkouts when the pipeline runs. When I then try to call a step with GitHubCommitStatusSetter, it then tries to set the status for both commits against both repositories (i.e. 4 different combinations of commit hash/repos). This results in {{FileNotFoundException}}s that fail the build. But this will obviously always fail because each commit is only valid for one of the repositories. I see I can hardcode repository and sha values, but unfortunately with the Github Organizational plugin, I don't have access to the sha directly. Is there anything that can be done to make this work? Thanks! Add Comment
[JIRA] (JENKINS-37834) Spacing and alignment of "action" icons is inconsistent
Title: Message Title Michael Neale edited a comment on JENKINS-37834 Re: Spacing and alignment of "action" icons is inconsistent Brody will soon have some screen/design input for this BTW (we got sidetracked on colours, but no change there for now) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37834) Spacing and alignment of "action" icons is inconsistent
Title: Message Title Michael Neale commented on JENKINS-37834 Re: Spacing and alignment of "action" icons is inconsistent Brody will soon have some screen/design input for this BTW Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31582) Log / document the plugin usage in the flow nodes
Title: Message Title Michael Neale commented on JENKINS-31582 Re: Log / document the plugin usage in the flow nodes sounds interesting. I think peoeple may put several line scripts, but not pages, so this may not be too bad. Regarding display, would be nice to show a summary of what it did (with ability to display the whole script invoked if warranted), could be quite neat. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38669) SCM (Git) Will Not Notify Pipeline Before Execution
Title: Message Title Dayton Gomez commented on JENKINS-38669 Re: SCM (Git) Will Not Notify Pipeline Before Execution Not really knowing anything at all about the inner workings of jenkins, I started digging around in the hopes that I'd find a workaround. Came across this line: https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitStatus.java#L300 With some console work, I came to find that scmTriggerItem.getSCMs() is empty until you the pipeline job is run at least once. After it runs, getSCMs() returns the same object references as project.definition.scm ... at least in my scenario. The object doesn't seem to change after the first run, at least as far as my little script sees. The data is for sure 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. F
[JIRA] (JENKINS-38394) Ability to set output of a step to environment variable(s)
Title: Message Title Patrick Wolf commented on JENKINS-38394 Re: Ability to set output of a step to environment variable(s) I think a generalized method to set the output of a step in an environment variable is a decent hack but it feels like a temporary workaround until the step is supported natively. Otherwise, a quick script block works just as well. For input I think we need a more elegant solution. I agree with Jesse Glick that input might require a more specialized setup in declarative. I think we should look into including an input section of the per-stage configuration like notifications. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36823) Upgrade AWS SDK to 1.11.16 to enable ecs-plugin to use Task Roles
Title: Message Title Jae Gangemi commented on JENKINS-36823 Re: Upgrade AWS SDK to 1.11.16 to enable ecs-plugin to use Task Roles is there any forward movement on 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-38564) API to convert json step blob to step syntax (and back) - one step at a time
Title: Message Title Michael Neale commented on JENKINS-38564 Re: API to convert json step blob to step syntax (and back) - one step at a time Yes rsandell that would do fine. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38394) Ability to set output of a step to environment variable(s)
Title: Message Title Michael Neale commented on JENKINS-38394 Re: Ability to set output of a step to environment variable(s) Patrick Wolf what do you think about a pipeline-model specific "captureInput" step - which wraps input and grabs its stuff as env vars? (may be easier than the changes needed to input?) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38622) Failed to load hudson.plugins.git.GitSCM
Title: Message Title Shoma Suzuki commented on JENKINS-38622 Re: Failed to load hudson.plugins.git.GitSCM Sorry for my invalid report of docker-jnlp-slave, it was updated. I'm trying to create minimum re-production environment. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38622) Failed to load hudson.plugins.git.GitSCM
Title: Message Title Shoma Suzuki updated an issue Jenkins / JENKINS-38622 Failed to load hudson.plugins.git.GitSCM Change By: Shoma Suzuki Environment: # java -versionopenjdk version "1.8.0_66-internal"OpenJDK Runtime Environment (build 1.8.0_66-internal-b01)OpenJDK 64-Bit Server VM (build 25.66-b01, mixed mode)# uname -aLinux jenkins-x-4ktxm 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux# base on jenkinsci/ docker-jnlp-slave jenkins:2.7 Docker image, running on Google Container Engine # Jenkins ver. 2.7.4# Plugins Name ↓Version Enabled Pinned ansicolor 0.4.2 true falsecredentials 2.1.5 true falsedisplay-url-api 0.5 true falseembeddable-build-status 1.9 true falseemotional-jenkins-plugin 1.2 true falsegit 3.0.0 true falsegit-client 2.0.0 true falsegithub 1.22.0 true falsegithub-api 1.77 true falsegoogle-login 1.2.1 true falsejunit 1.18 true falsemailer 1.18 true falsematrix-project 1.7.1 true falseplain-credentials 1.3 true falserole-strategy 2.3.2 true falsescm-api 1.3 true falsescript-security 1.23 true falseslack 2.0.1 true falsessh-credentials 1.12 true falsestructs 1.5 true falsetoken-macro 2.0 true falseworkflow-scm-step 2.2 true falseworkflow-step-api 2.4 true false Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38673) Update dependencies of plugins
Title: Message Title Thorsten Scherler updated an issue Jenkins / JENKINS-38673 Update dependencies of plugins Change By: Thorsten Scherler Sprint: pacific Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38673) Update dependencies of plugins
Title: Message Title Thorsten Scherler started work on JENKINS-38673 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-38673) Update dependencies of plugins
Title: Message Title Thorsten Scherler created an issue Jenkins / JENKINS-38673 Update dependencies of plugins Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Oct/04 12:53 AM Priority: Minor Reporter: Thorsten Scherler We need to update our dependencies for npm especially react (current version is 15.3.x) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38673) Update dependencies of plugins
Title: Message Title Thorsten Scherler assigned an issue to Thorsten Scherler Jenkins / JENKINS-38673 Update dependencies of plugins Change By: Thorsten Scherler 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-38248) Log should only be linkable from its line number
Title: Message Title Thorsten Scherler updated JENKINS-38248 Jenkins / JENKINS-38248 Log should only be linkable from its line number Change By: Thorsten Scherler 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-37017) Github Org folder projects detail screen missing org name in path
Title: Message Title Thorsten Scherler updated JENKINS-37017 Jenkins / JENKINS-37017 Github Org folder projects detail screen missing org name in path 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-36781) Display of SCM identifiers should be consistent
Title: Message Title Thorsten Scherler updated JENKINS-36781 Jenkins / JENKINS-36781 Display of SCM identifiers should be consistent 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-38011) Result header modal does not include full path
Title: Message Title Thorsten Scherler updated JENKINS-38011 Jenkins / JENKINS-38011 Result header modal does not include full path 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-37925) Show full log only shows 10000 lines
Title: Message Title Thorsten Scherler updated JENKINS-37925 Jenkins / JENKINS-37925 Show full log only shows 1 lines 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-26107) Allow stage to operate as a labelled block
Title: Message Title Kyle Flavin commented on JENKINS-26107 Re: Allow stage to operate as a labelled block Is the concurrency parameter no longer available? I'm converting some legacy code to use the new format. We have a lot of stuff that looks like this: stage name: 's1: do something', concurrency: 1 ... stage name: 's2: do something else', concurrency: 1 ... Maybe it's not necessary since we're setting the concurrency to "1" anyway? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title Juan Alvarez commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job Same here with Jenkins 2.7.2 and Build Pipeline Plugin 1.5.4. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38442) Support nested stages in the Pipeline Graph
Title: Message Title Kaden Wilkinson commented on JENKINS-38442 Re: Support nested stages in the Pipeline Graph Even the name of the script being called would help eg. sh 'script.sh' if the step was displayed as "script.sh" it would be much better than it is right now Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38442) Support nested stages in the Pipeline Graph
Title: Message Title Kaden Wilkinson edited a comment on JENKINS-38442 Re: Support nested stages in the Pipeline Graph I would like to have a syntax in the Jenkinfile to be able to say:{code: groovy java }sh([cmd: 'script.sh', name: 'Deploy script']) {code}or maybe something more generic that would work for all build steps?{code: groovy java }step('Deploy script') {sh 'script.sh'}{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-38442) Support nested stages in the Pipeline Graph
Title: Message Title Kaden Wilkinson edited a comment on JENKINS-38442 Re: Support nested stages in the Pipeline Graph I would like to have a syntax in the Jenkinfile to be able to say: ``` {code:groovy} sh([cmd: 'script.sh', name: 'Deploy script']) ``` {code} or maybe something more generic that would work for all build steps? ``` {code:groovy} step('Deploy script') {sh 'script.sh'} ``` {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-38442) Support nested stages in the Pipeline Graph
Title: Message Title Kaden Wilkinson commented on JENKINS-38442 Re: Support nested stages in the Pipeline Graph I would like to have a syntax in the Jenkinfile to be able to say: ``` sh([cmd: 'script.sh', name: 'Deploy script']) ``` or maybe something more generic that would work for all build steps? ``` step('Deploy script') { sh 'script.sh' } ``` Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33962) docker.inside broken on OSX
Title: Message Title Michael Neale commented on JENKINS-33962 Re: docker.inside broken on OSX Jesse Glick presumably if running inside a container, the docker daemon is bind mounted in so it can be accessed from the agent right? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38442) Support nested stages in the Pipeline Graph
Title: Message Title Michael Neale edited a comment on JENKINS-38442 Re: Support nested stages in the Pipeline Graph [~kdawgwilk] exactly - that is exactly what I was thinking. Do you want to label those steps explicitly, or if they showed a more helpful description (say, the first N chars of the script) would that help? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16327) Pages with CodeMirror editors are impossibly wide
Title: Message Title Ollie ! commented on JENKINS-16327 Re: Pages with CodeMirror editors are impossibly wide No, a combination of work commitments and my solution not being very good have been standing in my way. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37300) Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
Title: Message Title Klaus Schniedergers commented on JENKINS-37300 Re: Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder Running into the same issue when using latest LTS (2.7.4) plus "stable" plugins. Rolling multijob back to 1.21 fixes it, but I think it should be respun because otherwise every multijob user that updates plugins will see 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-38442) Support nested stages in the Pipeline Graph
Title: Message Title Michael Neale commented on JENKINS-38442 Re: Support nested stages in the Pipeline Graph Kaden Wilkinson exactly - that is exactly what I was thinking. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Michael Rose edited a comment on JENKINS-34439 Re: Clover plugin still has problems with pipeline builds I am seeing similar behaviour. The following error is in the console output: Originally I was seeing errors like this. When this was happening I would be able to access the Clover Summary Report but the Clover HTML Report was an empty page. {quote}IOException when checking workspace path:remote file operation failed: /JENKINS/WORKSPACE/PATH/FOR/PROJECT at hudson.remoting.Channel@7e2840c5:HOSTNAME: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@1359cfca{quote} Now, I am getting this error in the console output:{quote}java.lang.NullPointerException at hudson.FilePath.isAbsolute(FilePath.java:271) at hudson.FilePath.resolvePathIfRelative(FilePath.java:256) at hudson.FilePath.(FilePath.java:252) at hudson.FilePath.child(FilePath.java:1267) at hudson.plugins.clover.CloverPublisher.performImpl(CloverPublisher.java:161) at hudson.plugins.clover.CloverPublisher.perform(CloverPublisher.java:152) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:68) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:59) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745){quote}And the Clover Summary report in all builds now navigate to the oops page. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Ben Fortuna commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Antonio Muñiz Yes, this is a semi-workaround which I use - currently set to 7 day expiry. However for some projects the develop branch isn't built so frequently (i.e. greater than 7 days between builds) so the build history is lost (i.e. resets to build #1 which causes other issues such as versioning conflicts). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Michael Rose commented on JENKINS-34439 Re: Clover plugin still has problems with pipeline builds I am seeing similar behaviour. The following error is in the console output: IOException when checking workspace path:remote file operation failed: /JENKINS/WORKSPACE/PATH/FOR/PROJECT at hudson.remoting.Channel@7e2840c5:HOSTNAME: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@1359cfca Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38640) Unstash painfully slow for large artifacts (due to compression?)
Title: Message Title Andres Rodriguez updated JENKINS-38640 Jenkins / JENKINS-38640 Unstash painfully slow for large artifacts (due to compression?) Change By: Andres Rodriguez 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-38640) Unstash painfully slow for large artifacts (due to compression?)
Title: Message Title Andres Rodriguez assigned an issue to Andres Rodriguez Jenkins / JENKINS-38640 Unstash painfully slow for large artifacts (due to compression?) Change By: Andres Rodriguez Assignee: Andres Rodriguez Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38640) Unstash painfully slow for large artifacts (due to compression?)
Title: Message Title Andres Rodriguez started work on JENKINS-38640 Change By: Andres Rodriguez 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-36933) Name or alias Shell Script Step (sh)
Title: Message Title Kaden Wilkinson commented on JENKINS-36933 Re: Name or alias Shell Script Step (sh) This still doesn't solve 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-36933) Name or alias Shell Script Step (sh)
Title: Message Title Kaden Wilkinson updated an issue Jenkins / JENKINS-36933 Name or alias Shell Script Step (sh) Change By: Kaden Wilkinson Attachment: Screen Shot 2016-10-03 at 4.13.46 PM.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-29188) api URL for REST API is not available for flowGraphTable
Title: Message Title John Long commented on JENKINS-29188 Re: api URL for REST API is not available for flowGraphTable FWIW, I found some kind of API that seems to get this data. Doesn't seem official, but it is what the main Jenkins UI uses: http://:8080/job///wfapi wfapi seems to provide an entry point for lots of info about stages, steps and logs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38442) Support nested stages in the Pipeline Graph
Title: Message Title Kaden Wilkinson commented on JENKINS-38442 Re: Support nested stages in the Pipeline Graph I think the reason many are wanting to even have nested stages is to help solve this problem:We would like to give these shell scripts a more descriptive name but are unable to. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38442) Support nested stages in the Pipeline Graph
Title: Message Title Kaden Wilkinson updated an issue Jenkins / JENKINS-38442 Support nested stages in the Pipeline Graph Change By: Kaden Wilkinson Attachment: Screen Shot 2016-10-03 at 4.13.46 PM.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-38598) User can connect to Git with Username and Password
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38598 User can connect to Git with Username and Password Change By: Michael Neale Sprint: pacific Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38597) User can connect to Git with SSH key
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38597 User can connect to Git with SSH key Change By: Michael Neale Sprint: pacific Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38596) User can connect to a git repository
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38596 User can connect to a git repository Change By: Michael Neale Sprint: pacific Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9582) Ability to 'exclude' files in Archive for Clone Workspace SCM
Title: Message Title Owen Mehegan closed an issue as Fixed Jenkins / JENKINS-9582 Ability to 'exclude' files in Archive for Clone Workspace SCM Change By: Owen Mehegan 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-9473) Projects added to "Build other projects" action of "Promote builds" plugin don't appear as downstream jobs
Title: Message Title Owen Mehegan commented on JENKINS-9473 Re: Projects added to "Build other projects" action of "Promote builds" plugin don't appear as downstream jobs Oleg Nenashev I don't use this plugin anymore, feel free to close this 5 year old issue if you think it's no longer valid Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9473) Projects added to "Build other projects" action of "Promote builds" plugin don't appear as downstream jobs
Title: Message Title Owen Mehegan assigned an issue to Oleg Nenashev Jenkins / JENKINS-9473 Projects added to "Build other projects" action of "Promote builds" plugin don't appear as downstream jobs Change By: Owen Mehegan Assignee: 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-36288) JDL component for Popover
Title: Message Title Michael Neale started work on JENKINS-36288 Change By: Michael Neale 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-38596) User can connect to a git repository
Title: Message Title Michael Neale assigned an issue to Ivan Meredith Jenkins / JENKINS-38596 User can connect to a git repository Change By: Michael Neale Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38597) User can connect to Git with SSH key
Title: Message Title Michael Neale assigned an issue to Ivan Meredith Jenkins / JENKINS-38597 User can connect to Git with SSH key Change By: Michael Neale Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38598) User can connect to Git with Username and Password
Title: Message Title Michael Neale assigned an issue to Ivan Meredith Jenkins / JENKINS-38598 User can connect to Git with Username and Password Change By: Michael Neale Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33373) Rebuild open Merge Request
Title: Message Title Owen Mehegan closed an issue as Fixed Jenkins / JENKINS-33373 Rebuild open Merge Request Change By: Owen Mehegan 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-38672) Git Organization plugin bug
Title: Message Title M Yang created an issue Jenkins / JENKINS-38672 Git Organization plugin bug Issue Type: Bug Assignee: Unassigned Attachments: tsqe-generated-repo-folders.PNG, tsqe-org-folder.PNG, wrong-reference-of-branch.PNG Components: build-pipeline-plugin Created: 2016/Oct/03 9:40 PM Environment: Jenkins ver. 1.642.18.1 (CloudBees Jenkins Enterprise 15.11) Priority: Blocker Reporter: M Yang Github Organization Folder created jobs and folders that points to 404 url and wrong jobs. We have a github organization: tsqe In the org, there are couple repositories. When using Github Organization folder with jenkinsfile from SCM, the generated repository folders has mismatched job for branches. see attachments There are 4 repos under the org:, see tsqe-generated-repo-folders.PNG bbtf2 bbtfmini cloudbee_sample tsfixsim but within bbtf2, it has jobs created for >>bbtfmini>>master >>bbtfmini >> PR-222 These are just one example of this behavior. Because of these we are not able
[JIRA] (JENKINS-29188) api URL for REST API is not available for flowGraphTable
Title: Message Title James Sandlin commented on JENKINS-29188 Re: api URL for REST API is not available for flowGraphTable "Exposing an Api for what is already defined in the flow graph, or fixing some broken link perhaps." ? Jenkins UI is lacking and the tool itself is a huge security hole for large organizations (I run it for 300+ developers at a Fortune 500 company). We are required to have Jenkins behind a 2FA VPN, granting access to only my team. That said, we are working to provide the status view of the Pipeline Stage View to a custom / in house tool. We are able to access everything we need in Jenkins via REST API, and thus can provide the data. Sadly, we cannot show a live status of pipeline information. Is this data available elseware? I can get everything else I need via REST call / JSON. Why not the Pipeline phases? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38671) Email-ext plugin sending duplicate email notifications
Title: Message Title Shashi R created an issue Jenkins / JENKINS-38671 Email-ext plugin sending duplicate email notifications Issue Type: Bug Assignee: David van Laatum Attachments: duplicate emails.docx Components: email-ext-plugin Created: 2016/Oct/03 9:36 PM Environment: Jenkins 1.642.2 Priority: Blocker Reporter: Shashi R 12:26:48 Email was triggered for: Success 12:26:48 Sending email for trigger: Success 12:26:52 Sending email to: xxx...@x.com 12:26:52 [WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] done 12:26:52 Finished: SUCCESS The Console log shows that only one email is getting triggered on a success event. This is an expected result. However, there were multiple emails being sent with the same content, subject and at same time. To make sure that either of the emails are getting triggered for only success event, I gave single email address for success and 2 emails for fixed. As you can see, email is being triggered only in success event and my emails also have only one recipient in To: address. Please find attachment for Screen prints
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Roy Tinker commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level The workaround seemed to work, but then I got E200015: ISVNAuthentication provider did not provide credentials. I decided to dodge global pipeline libraries altogether and just checkout from SVN and load the pipeline library file directly. Here's what that looks like: https://gist.github.com/RoyTinker/69d0f1b962cb91336db4d2180934af3e Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Roy Tinker commented on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" I'm seeing this problem when attempting to configure a pipeline global library that checks out from SVN. I tried the above workarounds with no success. What finally worked for me was to completely dodge the global pipeline configuration - and manually check out and load the library in each pipeline instead. Here's what that looks like: https://gist.github.com/RoyTinker/69d0f1b962cb91336db4d2180934af3e Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37260) Add PATCH Mode
Title: Message Title Janario Oliveira closed an issue as Fixed Jenkins / JENKINS-37260 Add PATCH Mode Change By: Janario Oliveira 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-37260) Add PATCH Mode
Title: Message Title Janario Oliveira resolved as Fixed Jenkins / JENKINS-37260 Add PATCH Mode Change By: Janario Oliveira 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-37260) Add PATCH Mode
Title: Message Title Janario Oliveira started work on JENKINS-37260 Change By: Janario Oliveira 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-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_config_option.jpg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_option_config.jpg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_option_config.jpg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_for_manual_build.jpg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_option_config.jpg Attachment: Build_note_for_manual_build.jpg Attachment: popup_from_build_note_link.jpg Wish the following new feature can be added to the Build Pipeline Plugin:Add an option to show Build Note for Manual Build in the configuration. If the option is checked, a build note link will be displayed besides the trigger button, which can pop up a buildPipeline.fillDialog window for the user to enter values for parameters.I added this ability in my local with using another job (configured as a parameter) for entering build note . Please see the attached screenshots. It would be nice if the note can be entered to build job directly. It would be helpful if such an ability can be provided in a formal release.Thanks.Derek ![build_note_option_config](https://cloud.githubusercontent.com/assets/12051546/18797270/30c71f66-819b-11e6-9af5-b06d4b397e20.jpg)![build_note_for_manual_build](https://cloud.githubusercontent.com/assets/12051546/18797269/30c43396-819b-11e6-8f35-9278ad1cabb5.jpg)![popup_from_build_note_link](https://cloud.githubusercontent.com/assets/12051546/18797268/30c06716-819b-11e6-99f6-f70019dbde09.jpg) Add Comment
[JIRA] (JENKINS-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_for_manual_build.jpg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU updated an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Change By: DEREK LU Attachment: Build_note_option_config.jpg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38670) ability to enter build notes/parameters for a Manual step in the pipeline
Title: Message Title DEREK LU created an issue Jenkins / JENKINS-38670 ability to enter build notes/parameters for a Manual step in the pipeline Issue Type: New Feature Assignee: Unassigned Components: build-pipeline-plugin Created: 2016/Oct/03 8:50 PM Priority: Major Reporter: DEREK LU Wish the following new feature can be added to the Build Pipeline Plugin: Add an option to show Build Note for Manual Build in the configuration. If the option is checked, a build note link will be displayed besides the trigger button, which can pop up a buildPipeline.fillDialog window for the user to enter values for parameters. I added this ability in my local with using another job (configured as a parameter) for entering build note . Please see the attached screenshots. It would be nice if the note can be entered to build job directly. It would be helpful if such an ability can be provided in a formal release. Thanks. Derek ![build_note_option_config](https://cloud.githubusercontent.com/assets/12051546/18797270/30c71f66-819b-11e6-9af5-b06d4b397e20.jpg) ![build_note_for_manual_build](https://cloud.githubusercontent.com/assets/12051546/18797269/30c43396-819b-11e6-8f35-9278ad1cabb5.jpg) ![popup_from_build_note_link](https://cloud.githubusercontent.com/assets/12051546/18797268/30c06716-819b-11e6-99f6-f70019dbde09.jpg)
[JIRA] (JENKINS-34563) Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine
Title: Message Title Jesse Glick assigned an issue to stephenconnolly Jenkins / JENKINS-34563 Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine Change By: Jesse Glick Assignee: Kohsuke Kawaguchi 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-38666) Zero Length Space character in build history
Title: Message Title Daniel Beck commented on JENKINS-38666 Re: Zero Length Space character in build history Distinct from JENKINS-28022. Probably a bug in whatever code adds zero-width-spaces, I cannot think of a situation in which build numbers need that (at least not before going into the 5 digits or so). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38506) Invalid workspace path for pipeline jobs on jenkins master
Title: Message Title Mike Delaney commented on JENKINS-38506 Re: Invalid workspace path for pipeline jobs on jenkins master Nick Archibald while maybe not the best thing, you could use the 'ws' command to set a custom workspace for the build. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37925) Show full log only shows 10000 lines
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37925 Re: Show full log only shows 1 lines Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineRunDetail.js http://jenkins-ci.org/commit/blueocean-acceptance-test/70ad5394d4e566cf906a1a90822d32318a66f617 Log: JENKINS-37925 change full log link in steps to the backend log (#54) JENKINS-37925 change full log link in steps to the backend log JENKINS-37925 remove code instead of commenting 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-37925) Show full log only shows 10000 lines
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37925 Re: Show full log only shows 1 lines Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineRunDetail.js http://jenkins-ci.org/commit/blueocean-acceptance-test/a7a4984499af84acac4f7bd21c48f7d2c0a209b0 Log: JENKINS-37925 remove code instead of commenting 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-38669) SCM (Git) Will Not Notify Pipeline Before Execution
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-38669 SCM (Git) Will Not Notify Pipeline Before Execution 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.