By default, the p4 tickets are valid for 12 hours. You can request for
unlimited time access to p4 server from your perforce administrator and
they should be able to give you one.
Thanks,
JP
On Fri, Feb 27, 2015 at 11:05 AM, niraj nandane
wrote:
> the p4 commands that we execute in execute shel
the p4 commands that we execute in execute shell as a build step are saying
invalid or unset P4PASSWD.
This is because perforce gives 12 hrs of access to one login using p4
ticket.
How you are managing this invalid or unset P4PASSWD error ,that always come
after 12 hrs
--
You received th
On Thu, Feb 26, 2015 at 3:59 PM, wrote:
> Did you test my simple workflow?
No, sorry, was just guessing that your issue was a duplicate.
> Or is there as way for me to test it on a daily build of the plugin?
$ git clone https://github.com/jenkinsci/workflow-plugin.git
$ mvn -f workflow-plugin
Hi Jesse,
thank you for answering.
On Thursday, February 26, 2015 at 8:58:48 PM UTC+1, Jesse Glick wrote:
>
> On Tuesday, February 24, 2015 at 12:55:38 PM UTC-5,
> sebastien@gmail.com wrote:
>>
>> I still wonder wether this is a bug, which I should file, or not.
>>
>
> I did recently fix a p
Filed https://issues.jenkins-ci.org/browse/JENKINS-27152
Vincent
2015-02-26 21:23 GMT+01:00 Jesse Glick :
> On Thursday, February 26, 2015 at 1:11:23 PM UTC-5, Vincent Latombe wrote:
>>
>> Couldn't this be stored directly in a specific metadata folder outside of
>> any workspace?
>>
>
> Probably
And I just restarted Jenkins for the 2nd (or 3rd) time, and all of a sudden
it's working again. AARRGGHH
On Thursday, February 26, 2015 at 12:35:53 PM UTC-8, Vincent Latombe wrote:
>
> Hi,
>
> this seems to come from a bug from the Exclusion plugin (judging from the
> stacktrace).
>
> Vincent
>
Hi,
this seems to come from a bug from the Exclusion plugin (judging from the
stacktrace).
Vincent
2015-02-26 21:06 GMT+01:00 John Lussmyer :
> This just started today, and I have no idea what is causing it.
> Whenever I click on Save from Configure Project, I get this exception:
> (and my chan
On Thursday, February 26, 2015 at 2:55:17 PM UTC-5, Baptiste Mathus wrote:
>
> why aren't both of these just class
>> libraries for the groovy plugin with an easy way to add new ones for
>> common high-level operations?
>>
>
> Many reasons already given I guess (suspendable, etc.)
>
Right, the req
On Thursday, February 26, 2015 at 1:11:23 PM UTC-5, Vincent Latombe wrote:
>
> Couldn't this be stored directly in a specific metadata folder outside of
> any workspace?
>
Probably yes, so long as it is within the “slave root” folder, so you do
not get cross-device issues etc. Please file this s
On Thursday, February 26, 2015 at 1:13:00 PM UTC-5, Timothy Wojtaszek wrote:
>
> this means that for a node block, the master executing the workflow is
> effectively communicating with the slave for each command.
>
Correct, each `sh` step, etc. means a transaction starts over the remoting
channe
On Thursday, February 26, 2015 at 12:25:42 PM UTC-5, LesMikesell wrote:
>
> Workflow doesn't give you any access to the internals of the other
> jobs it can start, so you can't ensure that that all are building the
> same revision
https://issues.jenkins-ci.org/browse/JENKINS-26100
https://issue
On Wednesday, February 25, 2015 at 1:02:00 PM UTC-5, Alan Ray wrote:
>
> Is it possible to define a push trigger via the workflow?
>
Not sure offhand; it is quite possible that a modest change is needed to
the github plugin before this works.
Is there a way to (easily) answer this question via d
On Thursday, February 26, 2015 at 11:36:27 AM UTC-5, Rudy Gevaert wrote:
>
> Is there a way to make it more descriptive? Can we pass more parameters
> to the 'sh' call in the groovy.dsl?
> e.g.
>
> sh ( command: 'echo hello world', message: 'saying helo')
>
https://issues.jenkins-ci.org/browse/
Hi All,
If you are in the London area, pls join our Jenkins Workflow meet up:
http://www.meetup.com/jenkinsmeetup/events/219967721/
Seats are limited.
Cheers,
alyssa
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this g
This just started today, and I have no idea what is causing it.
Whenever I click on Save from Configure Project, I get this exception:
(and my changes aren't saved)
javax.servlet.ServletException: java.lang.NullPointerException
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
On Wednesday, February 25, 2015 at 11:00:11 PM UTC-5, Christoph Vogtländer
wrote:
>
> java.io.FileNotFoundException:
> D:\Jenkins\jobs\testjob\workspace\Binary\test.dll (Access is denied)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(Unknown So
On Tuesday, February 24, 2015 at 12:55:38 PM UTC-5, sebastien@gmail.com
wrote:
>
> I still wonder wether this is a bug, which I should file, or not.
>
I did recently fix a problem with the `stage` step not honoring
`concurrency` in some cases, which will go into 1.3.
https://issues.jenkins-
2015-02-26 17:09 GMT+01:00 Les Mikesell :
> On Thu, Feb 26, 2015 at 8:41 AM, Jesse Glick wrote:
> > On Thursday, February 12, 2015 at 10:43:28 AM UTC-5, LesMikesell wrote:
> >>
> >> With workflow, if you trigger another build, how do you access that
> >> other build object? For example to find t
Cool. I can simply strip off all the headers in a 1-line script and I'm left
with something usable as a standard changelog. Thanks!
-Original Message-
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Christopher Orr
Sent: February-26-15 13:5
On 26/02/15 08:15, John Mellor wrote:
I'd like to extract the git commit messages for the changes since the last
build, and insert them into the debian changelog in the product. This will in
many ways make each build self-documenting, and does things in a way that is
already very well support
2015-02-26 19:10 GMT+01:00 Vincent Latombe :
> As I understand it, this id is a hash of the workspace path already.
>
Actually some kind of uuid, after a second read ;)
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this
Thank you. I didn't fully appreciate that the workflow executes from the
master even within a node block. Just to be clear, this means that for a
node block, the master executing the workflow is effectively communicating
with the slave for each command. the node block simply sets the context
As I understand it, this id is a hash of the workspace path already. IMO
this is not something that should be exposed to the workspace (as the
control files are something Jenkins-internal), Couldn't this be stored
directly in a specific metadata folder outside of any workspace?
Vincent
2015-02-26
On Friday, February 20, 2015 at 4:01:35 PM UTC-5, Timothy Wojtaszek wrote:
>
> new File(root).eachDir { dirs << it.name }
>
You cannot use java.io.File methods from a Workflow script if you are using
slaves, since the script always runs on the master. If you need to inspect
files beyond what
On Monday, February 23, 2015 at 10:43:54 AM UTC-5, RM wrote:
>
> .6e6a43dd/jenkins-log.txt
>
> .6e6a43dd/pid
> .6e6a43dd/script.sh
>
>
> When i run 'git status' on my workspace using the shell command line, it says
> i have no untracked changes.
>
>
This control subdirectory is created for the dur
On Friday, February 20, 2015 at 12:41:03 PM UTC-5, Raul Ferriz wrote:
>
> Are there any existing and compatible checkstyle plugin with workflow?
>
https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md#build-steps-and-post-build-actions
does not list it, though I suspect this i
On Thu, Feb 26, 2015 at 9:10 AM, Jesse Glick wrote:
>
> But perhaps you meant the Build Flow DSL, which is quite different—a common
> source of confusion! This was actually the main “prior art” we considered
> while designing Workflow, and they have many similarities: both involve
> orchestrating
On Wednesday, February 25, 2015 at 8:42:40 AM UTC-5, Arek Skalski wrote:
>
> How can I use XUnit plugin within my workflow?
>
File an RFE in xunit-plugin with the label workflow, then ask to have it be
listed here:
https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md#build-s
On Thursday, February 19, 2015 at 1:11:53 PM UTC-5, Chris Taclas wrote:
>
> There may have been a problem with the way I had originally configured this
>
So some bug in Workflow, possibly filed, possibly not.
Is there a way to force kill these processes?
>
See the workaround mentioned here:
htt
I was the one filing https://issues.jenkins-ci.org/browse/JENKINS-26591 for
GHPRB and I also filed https://issues.jenkins-ci.org/browse/JENKINS-27136
for the general github push hooks
I need both for my projects.
On Thursday, 26 February 2015 16:49:45 UTC, Jesse Glick wrote:
>
> On Monday, Febr
On Friday, February 20, 2015 at 2:37:21 AM UTC-5, sebastien@gmail.com
wrote:
>
> why is the variable created by a "Boolean Build Parameter" (from the top
> of the job configuration page) not a boolean variable in the first place?
>
> I guess is has something to do with compatibility with non-
On Wednesday, February 18, 2015 at 6:18:03 PM UTC-5, Jos Backus wrote:
>
> How does one reference workflow steps like sh and build from inside an
> instance method? Using them unqualified yields a no method error.
If you are using the global class library system, read
https://github.com/jenkin
On Thursday, February 19, 2015 at 5:19:45 PM UTC-5, Scott Armit wrote:
>
> Does anyone know how to do this?
>
https://issues.jenkins-ci.org/browse/JENKINS-26133
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group an
On Thursday, February 19, 2015 at 9:03:51 AM UTC-5, Clifford Sanders wrote:
>
> extensions: [[$class: 'hudson.plugins.git.extensions.impl.CleanCheckout']]
>
Actually just $class: 'CleanCheckout' should suffice.
https://issues.jenkins-ci.org/browse/JENKINS-26619
--
You received this message beca
On Monday, February 16, 2015 at 1:08:42 PM UTC-5, Pedro Algarvio wrote:
>
> I need to be able to trigger builds from GitHub hooks, which is not yet
> supported I believe
>
Not clear if you are talking about JENKINS-26591 [1], for the pull-request
builder, or general GitHub push hooks, which wou
On Monday, February 16, 2015 at 8:51:39 AM UTC-5, sebastien@gmail.com
wrote:
>
> the test results from the two configurations are mixed in the
> junitResult.xml. All the test results are in the file, but their origin is
> lost.
>
> How could I get this feature back in my workflow job?
>
TB
Hello,
When I view the running steps page in a workflow job I just see: e.g.:
Git[image: Success]Shell Script[image: Console Output][image: Success]Shell
Script[image: Console Output][image: Success]Shell Script
Is there a way to make it more descriptive? Can we pass more parameters to
the
On Thu, Feb 26, 2015 at 8:41 AM, Jesse Glick wrote:
> On Thursday, February 12, 2015 at 10:43:28 AM UTC-5, LesMikesell wrote:
>>
>> With workflow, if you trigger another build, how do you access that
>> other build object? For example to find the build number so you can
>> copy its artifacts into
I'd like to extract the git commit messages for the changes since the last
build, and insert them into the debian changelog in the product. This will in
many ways make each build self-documenting, and does things in a way that is
already very well supported when building .debs.
Has anyone done
On Thursday, February 12, 2015 at 7:27:19 PM UTC-5, David Karr wrote:
>
> I was looking for a short statement that explains the difference between
> the workflow plugin and the dsl plugin
>
It is unclear which plugin you are comparing Workflow to.
If the Job DSL plugin, then Baptiste is correct:
On Friday, February 13, 2015 at 6:06:37 AM UTC-5, Stefan Lorenz wrote:
>
> Will this send the job to a queue if it's already running?
>
No, it will let a new build start, but then pause. Discussion:
https://issues.jenkins-ci.org/browse/JENKINS-26860
--
You received this message because you are
On Thursday, February 12, 2015 at 10:43:28 AM UTC-5, LesMikesell wrote:
>
> With workflow, if you trigger another build, how do you access that
> other build object? For example to find the build number so you can
> copy its artifacts into the workflow job.Or find the SVN_REVISION
> so you
Yup, I need to read closer. I use Build Flow not work flow
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jesse Glick
Sent: Wednesday, February 25, 2015 6:24 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: [workflow plugin] set build display nam
It's a dumb mistake.
We tested our Jenkins backup mechanism but forgot shutting it down.
Sorry for asking such a stupid question.
李大明於 2015年2月26日星期四 UTC+8下午5時51分17秒寫道：
>
> I have a Jenkins server which runs build verification by Gerrit Trigger
> plugin.
>
> This worked fine for months. But a
I have a Jenkins server which runs build verification by Gerrit Trigger
plugin.
This worked fine for months. But after last time I restart my Jenkins,
strange behavior happens:
Each Gerrit uploaded patchset will trigger two build. One is correct, but
the other use the build ID. Like:
Jenkins
Could you please explain deeply for mailer plugin.
Thanks
On Tuesday, February 24, 2015 at 5:40:51 PM UTC+5:30, slide wrote:
>
> It looks like your email settings are not correct, the Mailer plugin is
> not able to authenticate with the email server you setup.
>
> On Tue Feb 24 2015 at 4:36:16
46 matches
Mail list logo
