, 2016 at 6:50:02 AM UTC+10, Baptiste Mathus
> wrote:
>>
>> o/ Didn't check, but this should be in the "Snippet Generator".
>>
>>
>>
>> 2016-09-21 22:38 GMT+02:00 Åsmund Østvold :
>>
>>> Thank you Cuong and Michael,
>>>
>
;
>>> Cheers
>>>
>>>
>>>
>>> On Tue, Sep 20, 2016 at 10:47 PM, Baptiste Mathus
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> stage('tests') {
>>>> parallel 'longTests'
ail 1 sec
> build job: 'testjob2', quietPeriod: 0
> }, failFast: true
>
> }
>
> Cheers
>
> 2016-09-20 22:43 GMT+02:00 Åsmund Østvold :
>
>> hi All,
>>
>> Do anybody have an example or a pointer to how one could terminate a
>> parall
hi All,
Do anybody have an example or a pointer to how one could terminate a
parallel pipeline section on first failure?
The use case is that I have 14 tests in a checkin regression pipeline. Some
tests take 2 min some take 40 min. To speed up feedback to the users we
want to give feed back ASAP
Les, did you find a solution that worked for you?
Do anybody have a working solution they could share?
Regards,
Asmund
On Thu, Jan 8, 2015 at 12:40 AM, Jesse Glick wrote:
> On Wednesday, December 24, 2014 1:16:10 PM UTC-5, LesMikesell wrote:
>>
>> Is there - or could there be - a workflow step
I found that it was fixed with
https://issues.jenkins-ci.org/browse/JENKINS-31055. Sorry for the fuss...
Asmund
On Tue, Oct 27, 2015 at 10:37 AM, Åsmund Østvold wrote:
> I created https://issues.jenkins-ci.org/browse/JENKINS-31181
>
> On Mon, Oct 26, 2015 at 3:33 PM, Åsmund Østvo
I created https://issues.jenkins-ci.org/browse/JENKINS-31181
On Mon, Oct 26, 2015 at 3:33 PM, Åsmund Østvold wrote:
> Hi
>
> Setting a node temporarily to offline is not always persisted to disk.
> Normally this is not an issue but each time I have to restart Jenkins this
> a bi
Hi
Setting a node temporarily to offline is not always persisted to disk.
Normally this is not an issue but each time I have to restart Jenkins this
a big issue. I have 100+ nodes. The only way to update the temporarily
offline status is to change something in the node configuration and save.
Sa
thank you all for your input.
I am investigating to do a local change to build flow plugin.
Introduce a comment "//includefile " that is detected and
replaced it with the content of the file. I have a demo working.
What is missing is to be able to have a parameter as the second argument.
If you
hi all,
I want to thank Jenkins community for a this excellent tool.
To make my work even easier I would very much like to be able to do
regression testing on my build flow scripts. See [1] for motivation. If
anybody have solved this already I would very much like to know the
solution.
My sugges
s one:
> https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide&reset=true&jqlQuery=project+%3D+JENKINS+AND+status+in+(Open%2C+
> "In+Progress"%2C+Reopened)+AND+component+%3D+'reverse-proxy-auth'
>
> On 21.03.2014, at 14:05, Åsmund Østvold wrote:
>
> &
hi
Having just filled a ticket [1] in Jira for the Reverse Proxy Auth Plugin.
I checked the "Open Issues" link from the wiki page [2] and it did not
display my just submitted Jira ticket.
Have I done something wrong or have is the link in the wiki page wrong?
Åsmund
--
[1] https://issues.jenk
I am trying to upgrade reverse proxy auth from 1.0.1 to 1.3.2 and I am
having trouble [1].Jenkins version 1.532.2. If older release versions of
packages are available I could try to do the full update path version to
version.
If more information is needed please tell me. Any hit/quick fix is of
We are also interested. I may have time to contribute testing the RC. Is
there a list tests/taskes we can do to help the process along?
Asmund
Den 11. feb. 2014 18.30 skrev "Lynn Lin" følgende:
> We are also waiting for 1.532.2
>
> junkins 于2014年2月11日星期二写道：
>
>> I am waiting for 1.532.2 release
s@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Åsmund Østvold
> *Sent:* 28 October 2013 17:34
>
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: build flow, early exit from parallel construct?
>
> ** **
>
> Thank you James, ***
Thank you James,
I finally freed up some time and was able do a new stab at this. I have
inlined some questions and feedback.
On Fri, Oct 25, 2013 at 6:33 AM, James Nord (jnord) wrote:
> KillRunningjobs is called internally if the flow is aborted (or one of
> the jobs is aborted).
>
> Interna
o get the latest code and build it.
>
> ** **
>
> As always there may be other ways to achieve the same thing.
>
> ** **
>
> Regards,
>
> ** **
>
> /James
>
> ** **
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-us
Build Flow Plugin very useful plugging.
Is it possible to get the parallel construct to "terminate" still executing
jobs at first job exiting with none success? Or at least early fail the
job/section containing the parallel construct.
Use case is that I have a total long(30min) check-in regressio
I have seen similar issue. But only with jobs that have been renamed. Fix
for my instance is a restart of Jenkins. Build history come back.
Den 28. juni 2013 12.12 skrev "Louis Roché" følgende:
> I have the same problem. But my job has many build steps.
>
> I don't know why yet, but it's really a
Moving the thread to Jenkins user list
Sound like you have more or less what I have. But for easy access console
of the different jobs see the bottom part.
builds = []
ignore(FAILURE) {
parallel (
{ builds.add(build("foo1",
COPY_PATH : params["ba
My local build version of Jenkins have the same issue as ci.jenkins-ci.org.
It do not the list my rpm installed jenkins do:
https://ci.jenkins-ci.org/about/?
Build command I used for my jenkins.war was
mvn clean package -Dmaven.test.skip=true
Is there a build step I am missing?
Asmund
--
You
While doing bulk delete of builds I noticed that job health (weather) was
not reflecting builds present after a deletion.
I used groovy script provided by scriptler plugin:
import jenkins.model.*;
import hudson.model.Fingerprint.RangeSet;
def j = jenkins.model.Jenkins.instance.getItem(jobName);
/ pass
> fingerprints as you would do without build flow to orchestrate jobs
>
>
> 2013/1/17 Åsmund Østvold
>
>> I am investigating the build flow plugin and have hit a issue I am not
>> able to solve. What I want to able to copy artifacts from build job to
>> test jobs
I am investigating the build flow plugin and have hit a issue I am not able
to solve. What I want to able to copy artifacts from build job to test
jobs:
buildJob = build("buildBinaries")
parallel(
{ build("test1") },
{ build("test2") }
)
All projects need to be able to run concurrently(
I post the below to jenkins-user but did not get any feedback yet. I am
hoping that the Gerrit community can have some feedback.
Asmund
PS. I have dyslexia so if there may be things that are unclear. Feel free
to ask.
On Fri, Oct 12, 2012 at 9:48 AM, Åsmund Østvold wrote:
> I want to m
I want to make an automatic approve/promote ONE commit at a time with
multiple git repositories.
Background:
The issue is that a commits is too often breaking the product(dev env) and
causing productivity issues for the team.
- 10 git repositories.
- all 10 has unit tests.
- 50 Jenkins jobs in
just to terminate this thread.
This a issue with a mirror pointed to by
http://updates.jenkins-ci.org/update-center.json.
Asmund
On Mon, Aug 13, 2012 at 12:18 PM, Åsmund Østvold wrote:
> Thanks quick response.
>
> To validate if it is a local or a global (unlikely) issue. Could
Thanks quick response.
To validate if it is a local or a global (unlikely) issue. Could somebody
tell me what version of the git plugin that is available in there Jenkins
installation?
My Jenkins instances have 1.1.21 but I would expect 1.1.22.
Answers inlined.
On Mon, Aug 13, 2012 at 11:29 AM
Hi All,
My Jenkins instant do not get the latest plugin updates in the "update
center". I am able to install plugins. Example on old versions is that I
am asked if I want to upgrade the git plugin to 1.1.21. I know from [1]
that the news version us 1.1.22 and was released Aug 08, 2012.
Other b
My problem is that I have code that need a rebooted node. I have many long
running Jenkins test jobs that needs to be executed on rebooted nodes.
My existing solution is to define multiple "proxy" machines in Jenkins with
the same label (TestLable) and 1 executor per machine. I bind all the test
j
30 matches
Mail list logo
