On 25 September 2014 15:13, James Nord (jnord) wrote:
> > > What's the killer feature is
> > > 1) automatic (zero conf) finding of artifacts / test reports /
> > > findbugs report pickup etc etc...
> > >
> >
> > Well James, you do know *you* could use templates (as you have the
> > enterprise plu
> > What's the killer feature is
> > 1) automatic (zero conf) finding of artifacts / test reports /
> > findbugs report pickup etc etc...
> >
>
> Well James, you do know *you* could use templates (as you have the
> enterprise plugins ;-) ) and give a locked down build.
With literate? How - I did
code...
>
> /James
>
>
> > -Original Message-
> > From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> > Sent: 23 September 2014 19:44
> > To: Maven Users List
> > Subject: Re: usage with Jenkins
> >
> > FYI my aim is t
o...@gmail.com]
>> Sent: 23 September 2014 19:44
>> To: Maven Users List
>> Subject: Re: usage with Jenkins
>>
>> FYI my aim is to supersede the evil job type with some enhanced reporting in
>> what is currently called the literate job type.
>>
>>
e.
/James
> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: 23 September 2014 19:44
> To: Maven Users List
> Subject: Re: usage with Jenkins
>
> FYI my aim is to supersede the evil job type with some enhanced reporting in
> what is curr
On 23 September 2014 18:37, Curtis Rueden wrote:
> Hi James,
>
> > I can no longer see "Deploy artifacts to Maven repository"
> > as a post-build action.
>
> Just add a build step that does "mvn deploy" or similar.
>
See this for me is a post-build action. I guess Jenkins doesn't see it that
way
Thanks for the educations! :)
On Tue, Sep 23, 2014 at 3:55 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On Tuesday, 23 September 2014, Grover Blue wrote:
>
> > I'd like to weigh in on this. The maven-based job type is great for
> quick
> > or single-dimensional project, esp
On Tuesday, 23 September 2014, Grover Blue wrote:
> I'd like to weigh in on this. The maven-based job type is great for quick
> or single-dimensional project, especially when you know the scope will not
> change. I tend to prefer freestyle because of flexibility.
>
> In reality, the solution is
I'd like to weigh in on this. The maven-based job type is great for quick
or single-dimensional project, especially when you know the scope will not
change. I tend to prefer freestyle because of flexibility.
In reality, the solution is to just have one project type with varied
initialization typ
FYI my aim is to supersede the evil job type with some enhanced reporting
in what is currently called the literate job type.
That would mean you'd get the per-module reporting.
The current evil job type's other "killer" feature is automatic downstream
job triggering... Which is actually broken as
Hi James,
> I can no longer see "Deploy artifacts to Maven repository"
> as a post-build action.
Just add a build step that does "mvn deploy" or similar.
> Dare I ask what I'm missing having chosen the full-fat option..?
If you're asking what you cannot do with freeform jobs: I don't know of
an
That's interesting, James. Something to consider. We're using the open
source version of Artifactory, btw, and I the Artifactory Plugin has it's
own post build option. I'd probably use that.
Curtis, I had Netbeans create the new job for me through it's Hudson
plugin. It created a "multi-configur
News to me. Ironically I'm just setting up a new Jenkins job so tried the
freeform style - I can no longer see "Deploy artifacts to Maven repository"
as a post-build action.
Dare I ask what I'm missing having chosen the full-fat option..?
On 23 September 2014 14:02, Curtis Rueden wrote:
> The M
The Maven style build will also lock you in to a small subset of Jenkins's
usual features. And when you eventually need a feature not available with a
Maven-style build, there is no conversion path from Maven-style to
Freestyle -- you have to recreate the job (losing the build history etc.).
-Curt
Freestyle does not mess with your build and change it from building the way
maven intends. Google "stephen's java adventures Jenkins maven considered
evil" for a more detailed discussion
On Tuesday, 23 September 2014, James Green wrote:
> On 23 September 2014 02:23, Curtis Rueden > wrote:
> >
>
On 23 September 2014 02:23, Curtis Rueden wrote:
>
>
> Also, stay away from the Jenkins "Maven" style job. Freestyle is more
> flexible and less buggy.
>
Based on ..?
Hi Grover,
> CI build/packages successfully but not
> artifacts are listed on the jobs page
For Jenkins to publish artifacts (for any build, not just Maven-based ones)
you must use the "publish artifacts" option and specify the file path
patterns to publish.
Also, stay away from the Jenkins "Mav
Is there anything special that needs to be added to a pom in order to work
with Jenkins? For some reason, by CI build/packages successfully but not
artifacts are listed on the jobs page (they are hidden on the file-system
in a "default/*" directory).
18 matches
Mail list logo