My Jenkins job is aborted with the following message.. Strange thing is that it
completes every build step successfully.
Any idea what can cause that?
Build step 'Publish artifacts to SCP Repository' changed build result to ABORTED
Finished: SUCCESS
--
You received this message
I assume you want to have it do
for (item in Jenkins.instance.getAllItems(TopLevelItem.class)) {
println(Saving + item);
item.save();
}
otherwise you are only saving the items in the root and not all folders
(and the reason why I go for TopLevelItem is to filter out any of the evil
one's
Hi,
Doesn't have the desired effect, have run 2 variations on that, and it
doesn't have the same effect as just saving via the UI.
Possibly some plugins do some data migration and correct setting of
additional defaults when generating the form? and when this is post back it
results in the config
I wasn't saying for the UI version, rather I was pointing out to jieryn
On 16 October 2014 14:47, Darragh Bailey daragh.bai...@gmail.com wrote:
Hi,
Doesn't have the desired effect, have run 2 variations on that, and it
doesn't have the same effect as just saving via the UI.
Possibly some
So I have a job that sets to use a custom workspace with a directory of
C:\Chk, now, I'd like this directory to persist on a slave too on another
machine, but as you have to put a remote root directory you end up with the
slave creating folder along the lines of C:\C\Chk.
What's the correct
Oddly enough, if I set custom workspace and remote root both to C:\Chk this
works as intended, but that limits one job per node. :/
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from
On Thu, Oct 16, 2014 at 9:46 AM, Niksan sumot...@googlemail.com wrote:
Oddly enough, if I set custom workspace and remote root both to C:\Chk this
works as intended, but that limits one job per node. :/
No, if you run other jobs on that node they should be created as
C:\Chk\jobname\.
But
No, if you run other jobs on that node they should be created as
Unfortunately, my jobs are path length volatile, currently four characters
(I know, some constraints just suck). The jobs also have to be synchronous,
as in I can have two of them running together on a singular machine. If
That depends on what you mean by the rest of the path, the master suffers
from the same issue, I suppose one way would be to have the master not
perform any builds and somehow leverage the
hudson.model.Slave.workspaceRoot token and omit the workspace override on
the job, if any of that makes
On Thu, Oct 16, 2014 at 11:30 AM, Niksan sumot...@googlemail.com wrote:
That depends on what you mean by the rest of the path, the master suffers
from the same issue,
I mean, what is it that needs to use the full absolute path or even
its own working directory name? What keep you from putting
Hi,
Is there a way to modify the format of tagging revision names with the svn
plugin tag? For example instead of blah_blah-rev1 can I modify it to say
blah_blah-rev001 ?
This communication is for informational purposes only. It is not intended as an
offer or solicitation for the purchase or
Hi Jemes,
I don't think it can be possible, Since version number generated by SVN
Server. If it is possible you can misguide the people...
Regards,
Panikera
On Fri, Oct 17, 2014 at 12:34 AM, 'Jenkins, James W' via Jenkins Users
jenkinsci-users@googlegroups.com wrote:
Hi,
Is there a way
12 matches
Mail list logo
