On Fri, Jun 12, 2015 at 6:21 AM, Mads Nielsen wrote:
> What we noticed is that if we up the parent pom version from 1.532.3 ->
> 1.554.1 almost all our console output does NOT get displayed in the console
> out when we run our jenkins tests within jenkins (Regular
> System.out.println), we make
On Thu, Jun 11, 2015 at 11:55 PM, Kishore RP wrote:
> Using workflow plugin, our end users want to know what is
> happenning on a jenkins slave at some point of time by clicking on a
> hyperlink, (provide hyperlink for each slave)
Not sure I follow the question. The URL for the slave should show
Removed it.
Thanks.
On Friday, June 12, 2015 at 8:21:33 AM UTC-7, Christopher wrote:
>
> On 11/06/15 15:31, Jesse Glick wrote:
> > On Thu, Jun 11, 2015 at 1:19 AM, Wei Zheng > wrote:
> >> I have modified it now to use DockerRegistryEndpoint and verify that it
> works, and
> >> the plugin I a
On 11/06/15 15:31, Jesse Glick wrote:
On Thu, Jun 11, 2015 at 1:19 AM, Wei Zheng wrote:
I have modified it now to use DockerRegistryEndpoint and verify that it works,
and
the plugin I am asking for hosting (Google Container Registry Auth plugin)
works with this modification as well, no change
Don't forget to save the job after you've changed the branch, otherwise the
change will be lost after restart.
def job = manager.hudson.getItemByFullName("Target");
job.getScm().getBranches().get(0).setName("newBranch");
job.save()
On Fri, Jun 12, 2015 at 4:59 PM, Phil C wrote:
> Thanks Robert,
Thanks Robert,
I'm going to go with your solution. Executing this using the groovy
postbuild action works:
manager.hudson.getItemByFullName("Target").getScm().getBranches().get(0).setName("newBranch");
Phil
On Friday, June 12, 2015 at 7:05:22 AM UTC-7, Robert Sandell wrote:
>
> A plugin or g
For what it's worth, Phil, when I used the Job DSL plugin, I used it to
modify existing jobs. I admit it's been about a year since I worked with
it, but that's what we would do. We had it tied in with the job template
plugin, and I can't 100% remember which piece of it over-wrote existing
jobs, but
A plugin or groovy script could quite easily change the git branch of a
job, something like:
Jenkins.getInstance().getItemByFullName("Target").getScm().setBranch("newBranch");
But you could also try using the envinject plugin in Target to fetch the
contents of a stored artifact in the lastSuccess
Hi Ben,
Yes, I looked at the Job DSL plugin a bit. It looks like it currently only
provides the ability to create new jobs. I couldn't find a way to modify
an existing job. I only read through the documentation, and haven't
actually tried messing around with it yet though. Maybe I'm missing
Hi Richard,
Thanks for the suggestion.
Yes, we have tried parameterized builds. However, the unfortunate
disadvantage of having to provide parameters at build time is that humans
have to provide those parameters, and humans tend to make errors
(especially if they have to do it for every build
Phil, have you looked at the Job DSL plugin? It sounds to me like that
might be useful for you here.
https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin, and
https://github.com/jenkinsci/job-dsl-plugin/wiki
On Friday, June 12, 2015 at 1:05:48 AM UTC-4, Phil C wrote:
>
> Hi,
>
> I'd like
Hey fellow developers!
I have an issue which i am having a hard time finding out and fixing.
Basically, we have a test-suite which makes uses of custom test rules to
print information to the console about our tests, where we test a custom
tool with parameters and expected results.
What we noticed
12 matches
Mail list logo
