Hello Folks!
As my jenkins server is running in a subnet without internet access i was
wondering if it's possible to configure jenkins to check for plugin updates
on variable URL different from jenkins plugin centre one. We are going to
download content of plug in centre regularly and put it o
Most comfortable way would be to let jenkins update centre point to an URL
different from common one. But this is not manageable, is it?
--
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
ou need to cannot just use the same JSON (other download
> URLs), and need to sign the file contents.
>
> On 08.07.2015, at 08:40, jje > wrote:
>
> > Hello Folks!
> >
> > As my jenkins server is running in a subnet without internet access i
> was wondering
Okay... i've found a description how to make my own update centre.
"Wer lesen kann ist klar im Vorteil"
;-)
--
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 jen
al update centers on the Advanced tab of the
> plugin manager. Alternatively, UpdateSites Manager Plugin should be able to
> do replace the built-in update site.
> >
> > Remember that you need to cannot just use the same JSON (other download
> URLs), and need to sign the file co
ello Folks!
As my jenkins server is running in a subnet without internet access i was
wondering if it's possible to configure jenkins to check for plugin updates
on variable URL different from jenkins plugin centre one.
As prop'ed on
https://github.com/ikedam/backend-update-center2/wiki/How
As I've stated, i get null pointer exception in protected JSONObject
buildPlugins() -->Main.java;
There is no NULL Pointer check for this statement:
/**
* Build JSON for the plugin list.
* @param repository
* @param redirect
*/
protected JSONObject buildPlugins(MavenR
nterprise:
> https://www.cloudbees.com/products/cloudbees-jenkins-platform/enterprise-edition/features/custom-update-center-plugin
>
> It comes with a slick UI for managing either your own manually uploaded
> plugins or proxying the upstream OSS update centers, etc.
>
> On Thursday, July 9,
Further I've found out, that my local jenkins installation may be
corrupted. Did I get this right:
Either maven-created repo with plugins or jenkins installation with plugins
used is needed, isn't it?
Does creation of JSON with an other jenkins installation then the final one
used make a diffe
This statement may be false, as we enter listHudsonPlugis().
Right in there we gonna crash then
Am Donnerstag, 9. Juli 2015 16:35:51 UTC+2 schrieb jje:
>
> As I've stated, i get null pointer exception in protected JSONObject
> buildPlugins() -->Main.java;
>
> There i
etter soltuion
Am Freitag, 10. Juli 2015 08:56:44 UTC+2 schrieb jje:
>
> Further I've found out, that my local jenkins installation may be
> corrupted. Did I get this right:
> Either maven-created repo with plugins or jenkins installation with
> plugins used is needed, isn&#
given one means - plugins available on your jenkins plugin folder.
Am Freitag, 10. Juli 2015 10:35:42 UTC+2 schrieb jje:
>
> Now I've found out, that it does not matter, which installation is
> used(probably installed plugins are supposed to be available to final
> jen
headers of plugins
provided in step 1, which actually should match your content on plug-in
server.
Prost!!
Am Donnerstag, 9. Juli 2015 14:51:46 UTC+2 schrieb jje:
>
> ello Folks!
>
> As my jenkins server is running in a subnet without internet access i was
> wondering if it's
One more thing:
Null-Pointers are rather ugly..Finally reason for NULL-Ptr. exception
has been probably file-type which couldn't be handled(have seen some
backup-files e.g.). Havn't reproduced it yet.
Am Freitag, 10. Juli 2015 13:21:28 UTC+2 s
eated JSON though.
Cheers
Am Freitag, 10. Juli 2015 13:35:28 UTC+2 schrieb jje:
>
> One more thing:
> Null-Pointers are rather ugly..Finally reason for NULL-Ptr. exception
> has been probably file-type which couldn't be handled(have seen some
> backup-files e.g.). Havn'
Pls. note that our local repo containing plugin-files and jenkins master
reside in same network either.
Am Dienstag, 21. Juli 2015 15:50:11 UTC+2 schrieb jje:
>
> Last but not least:
>
> Gettin' metadata via browser(JSON Index File) is now working as expected.
> But it is
Last but not least:
Gettin' metadata via browser(JSON Index File) is now working as expected.
But it is nearly impossible to move jenkins to download plugins. Even
though either machine and jenkins user has access to local repository
granted, which actually has been tested by getting plugin fil
015 15:50:11 UTC+2 schrieb jje:
>
> Last but not least:
>
> Gettin' metadata via browser(JSON Index File) is now working as expected.
> But it is nearly impossible to move jenkins to download plugins. Even
> though either machine and jenkins user has access to local repository
Hi folks,
as I've noticed in syslog of jenkins master periodic backup plugin is being
run every minute, which is very confusing. As it was configured to run once
a day on 8 PM. What is the matter?
I've already tried hard to find related issues but I've rather found
nothing. But in different pos
Has somebody faced this issue? Periodically - once a week - jenkins seems
to loose control and goes crazy. After restarting jenkins service
everything seems to be alright. I'm not sure, if we had this issue before
upgrading master from 1.589, but i think so. Would be glad to get some
hints rela
Syslog looks like this.
Aug 23, 2015 6:50:35 AM hudson.model.AsyncPeriodicWork$1 run
INFORMATION: Started PeriodicBackup
Aug 23, 2015 6:50:35 AM hudson.model.AsyncPeriodicWork$1 run
INFORMATION: Finished PeriodicBackup. 1 ms
Aug 23, 2015 6:51:35 AM hudson.model.AsyncPeriodicWork$1 run
INFORMA
Don't mind second exception, explenation is marked yellow
Am Dienstag, 8. September 2015 07:44:40 UTC+2 schrieb jje:
>
> Find attached jenkins syslog. I've to admit log is pretty messy. Mainly
> exceptions are related to following topics:
>
>- connection proble
Don't mind second exception, explanation is marked yellow
Am Dienstag, 8. September 2015 07:44:40 UTC+2 schrieb jje:
>
> Find attached jenkins syslog. I've to admit log is pretty messy. Mainly
> exceptions are related to following topics:
>
>- connection proble
07:47:49 UTC+2 schrieb jje:
>
> Syslog looks like this.
>
>
> Aug 23, 2015 6:50:35 AM hudson.model.AsyncPeriodicWork$1 run
> INFORMATION: Started PeriodicBackup
> Aug 23, 2015 6:50:35 AM hudson.model.AsyncPeriodicWork$1 run
> INFORMATION: Finished Periodic
Okay. Thanks for that hint.
Am Dienstag, 29. September 2015 07:46:43 UTC+2 schrieb Richard Bywater:
>
> Argh - sorry folks. Looks like Inbox decided to requote the entire blob of
> stuff again :/
>
> Richard.
>
--
You received this message because you are subscribed to the Google Groups
"Jenk
Needless to say, that http-frontend is accessible, but it needs a lot of
time to load which seems very unusual to me.
--
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 ema
?
>
> 2015-10-12 13:36 GMT+02:00 jje >:
>
> Nope. It hungshere the current thread dump...
>
>
> Deadlock Detection:
>
> No deadlocks found.
>
> Thread 10059: (state = BLOCKED)
> - sun.misc.Unsafe.park(boolean, lo
Any updates on this issue...?
--
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.
To view this discussion on the web v
28 matches
Mail list logo
