Hi All
There are notes on how to install Jenkins.
But there's not many notes on how to upgrade Jenkins or migrate from Hudson.
Are there exact steps on how to upgrade (like what directories to copy
after deploying a new Jenkins war file)
so we don't miss any plugins, artifacts histories and job
co
Yes, you can change the branch specification later.
I myself always like to explicitly specify the branch instead of leaving it
blank. I really don't know what the git plugin does when you leave it blank. Is
there a reason why you cannot specify the name of the branch in the job
configuration?
I guess you are using git as your version control system and your question is
specific to the way the Jenkins git plugin works. It really would make
answering these questions a bit easier if people would tell a little bit what
kind of setup they have...
If the git plugin has been configured to
It looks like the artifact was being copied to a slave and the connection
broke. The reason is not clear from the stacktrace. Is there anything in the
logs on the slave side?
-- Sami
Chris Withers kirjoitti 29.1.2013 kello 14.21:
> Hi All,
>
> I've seen stack traces such as the following a c
It is not a good idea to run Jenkins as root. Unless you know what you are
doing. And even then it is not a good idea.
And if you do not know how to do it, you definitely should not be doing it.
Maybe instead you could explain what you are trying to do and why do you think
you need Jenkins to h
And if your slaves are not virtual machines, take a look at
https://wiki.jenkins-ci.org/display/JENKINS/PXE+Plugin or
https://wiki.jenkins-ci.org/display/JENKINS/Scripted+Cloud+plugin
-- Sami
Mark Waite kirjoitti 30.1.2013 kello 14.31:
> If you need to restore an existing operating system to
Which Jenkins version are you using? Recent Jenkins versions allowed
unauthenticated access to the slave-agent.jnlp URL, which makes starting JNLP
slaves a bit more difficult.
I'm pretty sure the slave startup does not use -auth option to provide a
username and password. Where did you pick that
Chris Withers kirjoitti 1.2.2013 kello 13.39:
> On 01/02/2013 11:30, Thomas Fields wrote:
>> Slave1
>> 1. Building project1, #345
>> 2. Building project2, #125
>> 3. Building project3, #455
>> 4. Building project4, #34
>> Building project5, #12
>> Building project6, #122
>> Building project7, #1
Did you upgrade or downgrade Jenkins? Has it restarted? What is in the log
file? Did you have job config history plugin installed? And if not, why? Is
your Jenkins configured to require login allowing changes?
-- Sami
Steve K kirjoitti 2.2.2013 kello 0.13:
> Has anyone else encountered this?
On Fri, Feb 1, 2013 at 7:36 PM, zw wrote:
> Hi Les
>
> Thanks for responding.
> We're new to Groovy too.
> Any concrete example to show how to get it to work on both platforms in a
> single job ?
Try the Xshell plugin with shell script (not extension) and batch
file (.bat) extension with the sam
Hello Chris.
The /toggleLogKeep URL in the job can do that.
For example:
http://[url]/job/[JOB-NAME]/20/toggleLogKeep
This URL will change the lock status of the build 20.
There's an interesting thing that you can use too: you can list all the
keep forever builds by using this URL:
http://
[ur
11 matches
Mail list logo