[JIRA] (JENKINS-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Justin Rainwater commented on JENKINS-38877 Re: Build History by Node doesn't work with Pipeline It's "resolved" because they're not gonna do anything about it. Regardless of how essential it may be. Our team has rolled our own solution which gets the job done despite requiring a ton of work. There's a reason Mr. Glick is suggesting everyone use Jenkins less. https://www.youtube.com/watch?v=Zeqc6--0eQw Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46163) Pipeline CPS Groovy does not seem to support spread '*' operator
Title: Message Title Justin Rainwater commented on JENKINS-46163 Re: Pipeline CPS Groovy does not seem to support spread '*' operator I just ran into this as well and I'm disappointed to see this was closed as a dupe when it's a different command. Any solution Andrew Bayer? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53258) Allow adding blue ocean only descriptive text
Title: Message Title Justin Rainwater created an issue Jenkins / JENKINS-53258 Allow adding blue ocean only descriptive text Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2018-08-27 17:34 Priority: Minor Reporter: Justin Rainwater I created a support issue last year https://support.cloudbees.com/hc/en-us/requests/52092 which led to this enhancement being added in BO 1.4: `-Dblueocean.feature.run.description.enabled=false` I really appreciate that change and it made BO work much better for us... However... It would be great if there were some way to set BO only descriptive text rather than having it mirror the build description and be an all or none sort of thing. We've had developers be confused by blue ocean results and if we could just add a bit of helper text at the top when we've detected certain results scenarios that it could reduce that confusion. Thanks Add Comment
[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title
Justin Rainwater commented on JENKINS-37491
Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
I wanted to add here a solution I found that feels like a nice workaround at least for my needs:
In GitHub Org options check to build both merged and unmerged PRs so you have a bunch of PR jobs ending in -merge and -head.
In the auto branch triggering field add PR-\d+-head so you auto build all head jobs but not all merge jobs. This will avoid the build storm that causes so many problems.
From inside the Jenkinsfile add something like this:
// have head job trigger merge job...
if (autoTriggered() && env.BRANCH_NAME.endsWith('head')) {
def headJobName = "${env.BRANCH_NAME}"
def mergeJobName = (headJobName.substring(0, headJobName.length() - 4)).concat('merge') // replace head with merge
build job: mergeJobName, wait: false
return
}
autoTriggered() is the function I added that returns false if cause description contains "Started by...". All this does is check if it's a head job and if so it triggers the corresponding merge job and exits. It feels a little too simple and too good to be true, but at first glance it seems like this gives best of both worlds of auto triggering merge jobs only on changes to head and avoiding the buildStorm.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Justin Rainwater commented on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes Related question: is there a way to differentiate whether a rebuild was triggered by update to base branch or head? I've setup our pipeline job so that I differentiate whether a job is manually or autotriggered by checking currentBuild.rawBuild.getCause(hudson.model.Cause$UserIdCause).properties.shortDescription for "Started by". It would be super helpful if the "Branch Indexing" message were more granular since I may want to take different action with my build depending on the event that triggered the hook, etc. Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Justin Rainwater commented on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes +1 to Spencer Malone's comment. I was hoping there might be an additional option in recent plugin updates to only rebuild PRs when folks commit to their PR and not when the base branch is updated. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Blue Ocean only for us as well. I never even saw a 404 page. In my case I just got a white screen of loneliness. The readme seems like a good place. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Yes thank you Kevin Burnett! I forwarded this info to our Jenkins admins. Turns out we use tomcat instead but they found the tomcat version of those commands as follows: -Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true -Dorg.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH=true Michael Neale is there somewhere this could be documented in case others run into it? This is a huge breakthrough for us. Now after months we can finally start playing with blue ocean! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Justin Rainwater commented on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes Is this addressed by the Github Branch Source updates? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39726) Don't rebuild all PRs on base branch update
Title: Message Title Justin Rainwater commented on JENKINS-39726 Re: Don't rebuild all PRs on base branch update I'm very excited to try v2.0.0 because this issue was blocking for us as well. Is there a way I could "watch" the releases of GitHub Branch Source plugin so I'm notified as soon as the official v2.0.0 is available? Thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012
Title: Message Title Justin Rainwater commented on JENKINS-33164 Re: Pipeline bat stuck on Windows Server 2012 We also hit this constantly on Win10. In our case it seems like if pipeline is trying to delete a running process then it will just be stuck there indefinitely. I can understand the headache of deleting files in use in general on windows, but I would hope that the Pipeline side of things could give up in accordance with the timeout settings we provide. Instead it will hang forever until we do the 3 step abort of terminating in the console. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Justin Rainwater commented on JENKINS-38877 Re: Build History by Node doesn't work with Pipeline @Joerg just so I understand correctly, are you saying "build display name" like using the name setter plugin? https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin Would you mind pasting in an example of what that end result name looks like? Since our pipeline jobs may run on 4-6 different nodes I can imagine having all of that information in a single build name getting a little unwieldy. Thanks, Justin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Justin Rainwater commented on JENKINS-38877 Re: Build History by Node doesn't work with Pipeline I agree that it's quite frustrating. It used to be you could at a glance see if a particular node was to blame for repeatedly failing jobs, but now with that information so buried it's not so easy. It seems we have to take matters into our own hands. One approach I'm looking into is to write the node name to currentBuild.description so at least when looking at the build history by job you can see the different nodes that ran each build. Better than nothing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Justin Rainwater updated an issue Jenkins / JENKINS-38877 Build History by Node doesn't work with Pipeline Change By: Justin Rainwater Comment: So in other words the "various longer-term plans for analytic capabilities" are in no way ready to be shared with users? I will most certainly not be holding my breath.Could you point me towards the documentation where it says the build history page should not be used 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-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Justin Rainwater commented on JENKINS-38877 Re: Build History by Node doesn't work with Pipeline So in other words the "various longer-term plans for analytic capabilities" are in no way ready to be shared with users? I will most certainly not be holding my breath. Could you point me towards the documentation where it says the build history page should not be used 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-39256) Allow stages to appear within nodes
Title: Message Title Justin Rainwater created an issue Jenkins / JENKINS-39256 Allow stages to appear within nodes Issue Type: Improvement Assignee: Unassigned Components: pipeline-view-plugin Created: 2016/Oct/25 10:20 PM Priority: Major Reporter: Justin Rainwater I think this issue may have already been raised or at least a similar version of it, but I couldnt find an example of exactly what I'm looking for. In a way this is the inverse of this other issue I logged: https://issues.jenkins-ci.org/browse/JENKINS-39119. In pre-pipeline Jenkins we'd have a single job that does git checkout, build, unit test, archive, etc. For pipeline we liked having these nice pretty stages for each of these steps. The problem is that the stash/unstash workflow really slows things down with the only benefit being the pretty stage display. If we put all of these steps into a single stage then it all works great, but then we just have this single green or red box which doesn't feel very 'pipeline-y'. We thought we solved everything when realizing we could save the node information between stages and force downstream stages to run on the same node. That way we could run in the same workspace and avoid the need for all the unstashing. The big catch with this approach is that between stages the node is briefly available so if another job is queued up then it will immediately grab it and the test stage will be stuck waiting for the now busy node. Our team has spent way too long trying to solve this core problem by trying our own methods of reserving a node by adding and removing node labels at the beginning and end of the pipeline. That however has created its own headaches in that modifying the labels doesnt seem reliable. We've also taken a look at the External Workspace Manager plugin but compiling a build over a network share is slower than doing stash/unstash. What would really solve things is if the stage view would let us parallelize for platform x config (so we're running say
[JIRA] (JENKINS-39119) Can't lock nodes between stages
Title: Message Title Justin Rainwater created an issue Jenkins / JENKINS-39119 Can't lock nodes between stages Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2016/Oct/19 6:56 PM Priority: Major Reporter: Justin Rainwater In an effort to balance speed with a satisfying stage view, we've taken steps to ensure that each stage runs on the same node. That way we dont have to stash/unstash too often because that is a big performance hit. For situations where we want to checkout source, configure, build and test it's fastest to just have this happen on the same workspace on the same node. The problem we've run into with this approach is that during that brief moment between a build and test stage for example, the node is available to all jobs and another job might grab it. We've attempted to work around this by getting clever with adding and removing node labels, but this creates all kinds of new bugs where labels don't get cleaned up or somehow a node ends up with labels from 2 different jobs at the same time. I thought I might have found something with https://github.com/jenkinsci/lockable-resources-plugin but that still feels like a manual process with creating "resources" that would apply to nodes and kind of faking that relationship by naming the resources the same as the nodes. The only way I can see at the moment to have the functionality and performance we're looking for is to combine all of the checkout+config+build+test into a single stage, but then we're losing much of what makes the pipeline workflow (and of course blue ocean) so useful. I would like to be able to grab an available node based on labels as I do now but have it stay reserved across stages until I explicitly say I'm done with it or the pipeline job is complete. If this can't be added as a new feature then any advice as to how to achieve this behavior with existing functionality would be much appreciated.
[JIRA] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title
Justin Rainwater edited a comment on JENKINS-34268
Re: Lock multiple resources using the Pipeline lock step
Just curious has anyone tried nested locking as a workaround? I'm curious if that would work.So instead of {code} lock (resources: ['resource1', 'resource2']) { ... execution block ... } {code} it would be: {code} lock('resource1) {lock('resource2) {... execution block ...}}{code :java } // Some comments here public String getFoo() {return foo;}{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-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title
Justin Rainwater commented on JENKINS-34268
Re: Lock multiple resources using the Pipeline lock step
Just curious has anyone tried nested locking as a workaround? I'm curious if that would work. So instead of lock (resources: ['resource1', 'resource2']) { ... execution block ... } it would be: lock('resource1) { lock('resource2) { ... execution block ... } }
// Some comments here
public String getFoo()
{
return foo;
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Justin Rainwater created an issue Jenkins / JENKINS-38877 Build History by Node doesn't work with Pipeline Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2016/Oct/10 11:36 PM Priority: Major Reporter: Justin Rainwater Browse to /computer//builds to see build history. For pipeline this page seems disabled. This is understandable because a single pipeline might span multiple nodes so showing a simple pass/fail list of pipeline jobs for a node might not make sense. However this has made it hard to tell at a glance when a certain node is failing more often than other nodes. I would like to see the build history page for nodes display the pipeline job name and build number and then maybe the stage name and step number or something that is definitely unique to that node. That way we could quickly browse history at the node level to determine if a particular node has problems. Add Comment
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders OK thanks. I have shown the problem to our internal jenkins admin so they will try to reproduce it as well. Must be something with our network. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Hello, I haven't tried these steps recently, but I just thought of something when I was looking again at the browser URL before meeting with our internal jenkins admins to ask them questions about our network. I notice in blue ocean that a job with folders will display sub jobs with a slash and then when you browse to that slash it encodes the slash to %2F. I suspect the key difference in being able to link directly to some URLs and not others is the presence of the %2F. I wonder if that gives you any leads to fixing the problem. Here's the last part of URL for the job that fails to load: /blue/organizations/jenkins/folder%2FmyJob/activity When in the normal view I see this: /job/folder/job/myJob/ which makes me think the %2F shouldnt be happening. Thanks, Justin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Uh... I'm confused by your response with instructions on how to check the console. My previous comment explained that I did check the console and it flashed a 400 error which I captured into an image which is attached. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Thanks I will try the newer betas. Checking console when refreshing window it flashes an error that was too quick to read, but I captured the frame from a gif. Seems to be a 400 when getting the job path. I had truncated the screen on purpose. Was there something you were hoping to see that wasnt included? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater updated an issue Jenkins / JENKINS-38210 Can't link to blue ocean jobs inside folders Change By: Justin Rainwater Attachment: 400_error.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-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater updated an issue Jenkins / JENKINS-38210 Can't link to blue ocean jobs inside folders Change By: Justin Rainwater Attachment: console_error.gif Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater updated an issue Jenkins / JENKINS-38210 Can't link to blue ocean jobs inside folders Change By: Justin Rainwater Attachment: console_error.gif Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders I have uploaded job_in_folder.gif. Yeah my steps are so simple that I wonder if it's something going on with our corporate network. What you don't see off screen in the gif is that I switch to blue ocean UI after building the vanilla job. Then when I get to list view showing the completed job I highlight the URL in address bar and press enter and everything goes white. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater updated an issue Jenkins / JENKINS-38210 Can't link to blue ocean jobs inside folders Change By: Justin Rainwater Attachment: job_in_folder.gif Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37843) REGRESSION direct link to a queued detail is not working anymore
Title: Message Title Justin Rainwater commented on JENKINS-37843 Re: REGRESSION direct link to a queued detail is not working anymore Thanks for the reply. I did a bit more digging and it seems to only apply to jobs created inside of folders. I've created this issue here: https://issues.jenkins-ci.org/browse/JENKINS-38210 Since all of our existing jobs are inside a folder this is quite the blocker for us. Thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater created an issue Jenkins / JENKINS-38210 Can't link to blue ocean jobs inside folders Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/14 5:34 PM Environment: OS X 10.11.4, MacBook Pro Chrome 52 Jenkins 2.7.3 BlueOcean beta 1.0.0-b05 Priority: Major Reporter: Justin Rainwater 1. In regular Jenkins view click New Item, enter Item Name, select Folder and click OK. 2. Click Save on folder config page then click link to create a new job inside the folder. 3. Add a name for the job, select Freestyle Project and click OK. 4. Click Save in config page then click TRY BLUE OCEAN UI at the top. 5. Click the path in the list that matches the folder/job you just created (jenkins/myFolder/myJob) 6. The url should now end with /activity. Click Refresh Result: Screen doesn't load. Same as if you try to go to this link directly. Add Comment
[JIRA] (JENKINS-37843) REGRESSION direct link to a queued detail is not working anymore
Title: Message Title Justin Rainwater edited a comment on JENKINS-37843 Re: REGRESSION direct link to a queued detail is not working anymore I found this issue searching for "direct link". The initial steps sound specific to queued runs although for me it applies to viewing all jobs of any kind. It seems we can't share links directly to a job in progress and we always have to start at the `/blue/pipelines/` level and from there click the pipeline name and the build # to get back to the pretty flowchart view.Adding my vote for this issue because I can't imagine being able to use my team using this plugin without being able to link directly to a specific build result. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37843) REGRESSION direct link to a queued detail is not working anymore
Title: Message Title Justin Rainwater commented on JENKINS-37843 Re: REGRESSION direct link to a queued detail is not working anymore I found this issue searching for "direct link". The initial steps sound specific to queued runs although for me it applies to viewing all jobs of any kind. It seems we can't share links directly to a job in progress and we always have to start at the `/blue/pipelines/` level and from there click the pipeline name and the build # to get back to the pretty flowchart view. Adding my vote for this issue because I can't imagine being able to use this plugin without being able to link directly to a specific build result. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38129) pipelines stopped working after update to 2.22
Title: Message Title Justin Rainwater commented on JENKINS-38129 Re: pipelines stopped working after update to 2.22 I found this bug by searching online for the error message. I was able to resolve it by using the pipeline syntax snippet generator, to change all of my properties away from the old $class style. However I see from Jenkinsfile that the gitlab parameter is the only property you have using $class and I dont see gitlab as an available parameter in the snippet generator so maybe that won't help in your case. Either way I think a more accurate description of this issue would be gitlab specific rather than just "pipelines stopped working" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38129) pipelines stopped working after update to 2.22
Title: Message Title Justin Rainwater edited a comment on JENKINS-38129 Re: pipelines stopped working after update to 2.22 I found this bug by searching online for the error message. I was able to resolve it by using the pipeline syntax snippet generator, to change all of my properties away from the old $class style. However I see from your Jenkinsfile that the gitlab parameter is the only property you have using $class and I dont see gitlab as an available parameter in the snippet generator so maybe that won't help in your case.Either way I think a more accurate description of this issue would be gitlab specific rather than just "pipelines stopped working" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27916) GString not flattened to String by DSL inside a map
Title: Message Title
Justin Rainwater commented on JENKINS-27916
Re: GString not flattened to String by DSL inside a map
I found this thread because I was running into the exact same error. I was able to get it working by adding .toString() along with the () in the mapping. So in this case it would be: def file = "name-$ {env.BUILD_NUMBER} ".toString() [(file) : "."] HTH
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
