Hello Kamaha Claude,
I hope Mark Waite and Martin d'Anjou's replies help you in getting started.
Curiously, did you learn about Jenkins via your school, University of Buea
in Cameroon? Recently, I contacted schools worldwide about Jenkins Google
Summer of Code, including your university in
On Fri, Nov 30, 2018 at 8:59 AM Staffan Forsell wrote:
> artifact-manager-s3 seems to contain examples of most of the things needed.
Too complicated for your purpose. Creating a plugin with a lightly
edited clone of `StandardArtifactManager` would suffice. (Use the
Maven archetype for a plugin
Well, we have lots of jobs, both freestyle and different styles of the new
pipeline, not all for sw that's currently in active development but we still
need to know we can build these.
We would rather invest our time in something that's useful for all jobs without
changing all those old job
The simplest approach, starting from what you are doing now, would be
to keep the build records and other state files from your Jenkins
installation, recreating only the configuration files from Git.
--
You received this message because you are subscribed to the Google Groups
"Jenkins
On Fri, Nov 30, 2018 at 8:59 AM Staffan Forsell wrote:
> Another way of doing this would be to just invest in lots of SSD storage for
> our jenkins servers.
Or just changing your projects to deploy artifacts to a proper
repository manager. The `archiveArtifacts` step and its kin is
intended
I'd also be interested in this SIG.
On Thu, Nov 29, 2018 at 8:26 PM arch wrote:
> Collect the feedbacks from the contributors and users is important. Share
> the questions and experience could let Jenkins community become stronger.
>
> On Fri, Nov 30, 2018 at 6:19 AM wrote:
>
>> I would very
On Thu, Nov 29, 2018 at 3:33 PM Oleg Nenashev wrote:
> I will ask the maintainers
I do not know if there _are_ any maintainers. Not me.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving
we solved this in Jenkins X through the use of Prow for handling webhooks &
orchestrating the serverless jenkins pod and then using kubernetes custom
resources to maintain state (pipeline activities, environments, teams,
releases etc)
https://jenkins-x.io/news/serverless-jenkins/
we then use an
artifact-manager-s3 seems to contain examples of most of the things needed.
I did not quite understand...do you recommend against trying to do this or
something else? If we would implement the same tests and use the same key
as artifact-manager-s3, I would thing it would not be unreasonable
Hi,
Since we now have JCasC and the job-dsl plugin it is easier then ever to treat
jenkins as a disposable resource and just recreate it from scratch whenever you
feel the need for it.
We do have build everything around this idea and reinstall our whole build
infrastructure every time we need
Implementation is quite easy I would say.
You need an ArtifactManager (look at the StandardArtifactManager, you
can probably just copy and replace the getArtifactsDir() method)
And an ArtifactManagerFactory where you can configure the root path for
the artifacts
On 30.11.2018 10:40, Staffan
I'm actually using VS Code + Maven plugin on Windows (and I'm a newbie on
that front) to build the plugin.
If I do a "clean" before every "compile" it works... a bit inconvenient,
but it works.
Thanks for your help.
Am Freitag, 30. November 2018 10:32:25 UTC+1 schrieb Daniel Beck:
>
>
Hello,
I have been looking for a way moving the artifacts out of the builds
directory and have been looking at the ArtifactManager.
Is there a reason that I can't find an implementation of this that just
uses a different local directory on the master?
Would should an plugin be hard to implement
Configure your IDE to include the generated sources directory in the sources
(or just build with Maven).
https://github.com/jenkinsci/cppcheck-plugin/blob/c81b79534602f258216096170c091ad31f8b7e60/pom.xml#L154
> On 30. Nov 2018, at 10:10, Thomas Döring wrote:
>
> Hi everyone,
>
> I'm trying
Hi everyone,
I'm trying to compile the cppcheck-plugin with the GitHub sources. The
build fails because the `org.jenkinsci.plugins.cppcheck.model.*` sources
are missing.
[ERROR] /d:/Projects/GitHub/thomas-dee/cppcheck-plugin/src/main/java/com/
15 matches
Mail list logo
