Hi everbody,
i have starte with GITLab and Jenkins and hanging on a problem.
When i try to connect with jenkins on GITLab repo he gives me the following
error.
Failed to connect to repository : Command "git ls-remote -h
https://mydomain.local.git HEAD" returned status code 128:
stdout:
stderr
steps {
sh "env"
}
}
}
}
Does anyone know the ratio behind this?
TIA
Sascha
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails f
On Wednesday, 16 August 2017 12:36:05 UTC+2, Victor Martinez wrote:
>
> Hey,
>
> It seems you are missing the displayVersion and valueExpression attributes.
>
Thank you! :)
It seems that the displayVersion Parameter must not be null. :/
Thanks again
Sascha
--
You received this
[$class: 'InlineJsonDataProvider',
autoCompleteData: '[{"id":"1"},{"id":"2"}]'
)
}
}
}
}
How do I use the InlineJsonDataProvider correctly?
Jenkins V 2.60.2
Autocomplete Parameter
Also the problem with this execution is that
cd "/home/jenkins/workspace/slave-test-npm"
makes a
dir('') {
// some block
}
not working.
Am Freitag, 24. März 2017 12:45:00 UTC+1 schrieb Sascha Vujevic:
>
> Hello developers,
>
> we use the kubernetes-plu
script.sh' >
'/
home/jenkins/workspace/slave-test-npm@tmp/durable-fc339069/jenkins-log.txt'
2>&1
; echo $? >
'/home/jenkins/workspace/slave-test-npm@tmp/durable-fc339069/jenkins
-result.txt'
Could this output be avoided ?
Thanks for your support.
Best rega
; On Fri, Mar 17, 2017 at 12:40 PM, 'Sascha Vujevic' via Jenkins Users <
> jenkins...@googlegroups.com > wrote:
>
>> Hello developers,
>>
>> i don't know if i use the kubernetes-plugin correct:
>> My jenkinsfile looks like:
>>
>
Hello developers,
i don't know if i use the kubernetes-plugin correct:
My jenkinsfile looks like:
podTemplate(label: 'mypod', containers: [
containerTemplate(name: 'maven', image: 'myOwnMavenImage:latest'',
ttyEnabled: true, command: 'cat')
]) {
node ('mypod') {
Hi Vincent,
1.5.2 works fine. Thanks for the assistance and the fix.
Sascha
Am Montag, 7. Juli 2014 09:54:10 UTC+2 schrieb Vincent Latombe:
>
> I just released 1.5.2 with the form fix.
>
> Vincent
>
>
> 2014-07-07 9:07 GMT+02:00 Sascha Herrmann >:
>
>> Hi!
&g
Hi!
Thanks. It seems to be just a thing of saving the setting. When I put the
"2" directly into the endViewDelay tag in the XML and then restart Jenkins,
then the delay is applied fine and I see the "2" in the settings.
Sascha
--
You received this message because you a
Hi!
Version 1.5.1 doesn't work or I am doing it wrong.
I set the delay to "2" in the settings, but when I come back to the
settings after saving, it's "0" again, and there is no delay applied in
endview according to the logs.
Sascha
--
You received this message
Hi Vincent,
sure that's okay. I was going for a simple system property since the error
(from your reaction) seemed a bit exotic and has only been reported by me
so far.
But configuration in the plugin settings is great, thanks. So I will not
create that pull request,
Sascha
Am Monta
That was quick. It doesn't work. Immediate timeouts after endview again.
Sascha
Am Montag, 30. Juni 2014 12:21:00 UTC+2 schrieb Sascha Herrmann:
>
> Hi Vincent,
>
> thanks. I will try. I doubt that it will bring an improvement, because
> we're already ending the view_s
Hi Vincent,
thanks. I will try. I doubt that it will bring an improvement, because
we're already ending the view_server processes after the build using a
batch script as I mentioned previously.
I will update the post with my findings.
Thanks again.
Sascha
Am Montag, 30. Juni 2014 09:
Builds run fine now. Seems that endview takes some time to finish before
the next command can be called.
Would it be possible to get a delay like that into the official plugin?
Maybe configurable with a system property?
Sascha
Am Freitag, 27. Juni 2014 08:56:09 UTC+2 schrieb Sascha Herrmann
obably too much, yes. Just wanted to be on the safe side
for the test.
First build flows ran successfully. Seems to confirm that there is a timing
problem in our environment.
Will update the thread with the results in a couple of days when I know for
sure.
Sascha
--
You received this message b
views (also the views we were using for
Crucible) to snapshot views.
Sascha
Am Dienstag, 24. Juni 2014 08:52:22 UTC+2 schrieb Dirk Heinrichs:
>
> Am 23.06.2014 10:15, schrieb Sascha Herrmann:
>
> But there seems to be a (hardcoded?) limit of how many view_server
> processes the
7;s an OS limit.
Sascha
--
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 it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit ht
art it again?! I have no other explanation for an immediate
timeout. But that's just guesswork of course.
Thanks for your reply.
Sascha
Am Montag, 23. Juni 2014 10:39:22 UTC+2 schrieb Jes Struck:
>
> Hey sascha,
>
> with out vein an expert in this specific plugin, could you maybe tell if
cleartool. Only way to stop these was to end the view_server process after
a build (these processes tend to linger, one per view, if we don't).
No such thing as a limit command on Windows.
Sascha
Am Montag, 23. Juni 2014 10:39:22 UTC+2 schrieb Jes Struck:
>
> Hey sascha,
>
> with o
Which is a fine workaround. But it would
be great if the plugin would feature an option to end the view after the
checkout. Not sure if that makes sense in general. It would for us. That's
more like a feature request :o)
Regards,
Sascha
--
You received this message because you are su
Hi James,
thanks for you assistance.
Sascha
Am Freitag, 4. April 2014 22:49:15 UTC+2 schrieb teilo:
>
> Hi Sascha,
>
> Fix is at https://github.com/jenkinsci/build-flow-plugin/pull/42 if you
> want to get the source and do a local build.
> Otherwise wait for the code to be a
overhead. The GET request is then some
6522 bytes.
When you talk about a fix ... how would we get the fix? Will it go into the
next plugin version?
Sascha
Am Mittwoch, 2. April 2014 22:36:57 UTC+2 schrieb teilo:
>
> Sounds like the flow is validating the dsl via a http get request.
> If
ration pages of build flows. We have hundreds
of build jobs. Only the flows show that behaviour. The DSL of the flow is
correct. The flows itself run without problems. Problem happens when I try
to configure the flow.
The error log reveals nothing.
Thanks.
Sascha
--
You received this messa
Hi all,
does anybody know off a way, to let the gerrit trigger plugin set the
build participants? As Jenkins doesn't know who participated, Jenkins
cannot bug people via Jabber / XMPP or count the CI game scores for them.
Any tips where to look at would be highly welcomed!
Greetings
-S
Hi everyone,
I have a very simple MSBuild project in Jenkins that produces code coverage
information.
When trying to use the link provided by Html Publisher Plugin in the
project view I get an 404 error:
Status Code: 404Exception:
Stacktrace:
(none)
--
*Generate
ated. There are many good tutorials for using CVS with ANT. And you
can simply "invoke ANT" into a jenkins job (with monitoring).
Regards
Sascha
2012/8/6 Rodri
> Hi,
> After following all the instructions above:
>
>- Jenkins conf -> CVSROOT = :ext::
>- Env var
Hi,
I had the same problem with the SSH connection for a CVS export with
Jenkins-CI.
The solution was to convert the PuTTy-generated SSH .ppk into an OpenSSH
file. After that it works great!
Regards,
Sascha
On Wednesday, May 2, 2012 2:41:13 PM UTC+2, Xavier NOPRE wrote:
>
> Hi,
>
&g
28 matches
Mail list logo