Hello Dan,
I started as a normal Python developer, then built and led a team of test
automation engineers while the management decided to switch to Java 10
years back and inherited CruiseControl, which we dropped for Hudson. I had
some small scale operating experience as well (email
Hi
Thank you for the great advice, I can come to a conclusion to train a team
internally from ground up
-Dan
On Sun, May 31, 2015 at 11:21 PM, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello Dan,
I started as a normal Python developer, then built and led a team of test
automation
For my case, I am very fortunate to involve with the the product from early
day (a year ba ck) and Maven is embraced to the max where plugins are
developed to solve every build use case in a full dev/qa/releng integration
pipeline. The developments are multi-sites and heavily depending Maven
First, treating build as a separate discipline from code is, in my
experience, a recipe for trouble. The poms or build.xml or whatever
files are just as much part of the source code as the java. Someone
may own Jenkins or whatever, but the devs should own the building of
the code they write.
On 1 June 2015 at 09:40, Dan Tran dant...@gmail.com wrote:
For my case, I am very fortunate to involve with the the product from early
day (a year ba ck) and Maven is embraced to the max where plugins are
developed to solve every build use case in a full dev/qa/releng integration
pipeline.
I'm sure I've said it before, but part of Maven's problem is that this is
all magically taken care of behind the scenes and less people need to know
how it works to make it work.
The downside is that there are then less people who can fix things when
they need fixing.
Exactly, it is hard
Hello Dan,
we treat tooling like software as well. Ticket creation is an automated 2
click process and the package qa will not take more than 5 minutes for
small changes.
External libraries from central may be used at free will, but we recommend
stuff in a so called toolbox, these dependencies
Hi Curtis,
It is an awesome info and process, I have a long way to catch up
Thanks
-Dan
On Sun, May 31, 2015 at 2:36 AM, Curtis Rueden ctrue...@wisc.edu wrote:
Hi Dan,
PS. Would love to hear other experiences from community rather me
sucking out Mirko's :-)
Not sure how relevant my
Hi Mirko,
Looks like the topic getting very interesting here, but I would like to
refocus on the skillset
How did you form up your team?, did you all pickup Java before joining this
devops team?
Thanks for all the sharing
-Dan
PS. Would love to hear other experiences from community rather me
Hi Dan,
PS. Would love to hear other experiences from community rather me
sucking out Mirko's :-)
Not sure how relevant my scenario is, but here goes:
My group consists of an international collaboration of OSS developers at
universities etc., rather than a company. But a lot of our needs are
On 30/05/2015 10:44 PM, Dan Tran wrote:
Hi Ron
One person may not be desirable since he/she may win a lottery :-)
I sell Learning Management Systems that include Talent and Succession
Planning so I will just say that you should be able to find a backup in
your pool of potential successors
What I forgot:
patience, social skills and remembering that not every application
developer needs to be a build specialist are important as well :-)
Regards
Mirko
--
Sent from my mobile
Am 30.05.2015 07:29 schrieb Dan Tran dant...@gmail.com:
Hi
I would like to ask if the community can
Thanks Mirko
* What about snapshot and release policy, do developers/qa have access to
deploy snapshot and release artifacts?
* do you use artifact signing similar to Maven Central?
Thanks again
-Dan
On Sat, May 30, 2015 at 9:21 AM, Mirko Friedenhagen mfriedenha...@gmail.com
wrote:
Hello Dan,
- Every developer may deploy SNAPSHOTs, however this is normally done
by Jenkins.
- We do not enforce staging from Jenkins, however almost all projects
do this. We do not enforce this, so Jenkins outages do not inhibit
releasing hot fixes.
- Releases are deployed to a staging
Hi Mirko
Looks like you have Artifactory to store all of release artifacts and
another 'release' repo to store the final approved release
Is internal tooling, thirdparty upload going thru the same release process?
Thanks
-Dan
On Sat, May 30, 2015 at 2:41 PM, Mirko Friedenhagen
On 30/05/2015 1:29 AM, Dan Tran wrote:
Hi
I would like to ask if the community can share with me what it takes to
maintain an enterprise build system with continuous integration of 100+
developer + QA and growing using Maven. The build system contains many
components with their own release
Hi Ron
One person may not be desirable since he/she may win a lottery :-)
Developers should not change the POM who would? RelEng?
Thanks
-Dan
On Sat, May 30, 2015 at 3:22 PM, Ron Wheeler rwhee...@artifact-software.com
wrote:
On 30/05/2015 1:29 AM, Dan Tran wrote:
Hi
I would like to
Hello Dan,
currently I have a team of two (with me three) devops guys.
We provide 30 Jenkins masters with 20 build nodes and about 1800 jobs which
we provision ourselves as well (Debian is already installed and we are able
to login via ssh).
We provide the department pom, some Maven plugins,
Hi
I would like to ask if the community can share with me what it takes to
maintain an enterprise build system with continuous integration of 100+
developer + QA and growing using Maven. The build system contains many
components with their own release cycle and they do integrate together.
19 matches
Mail list logo
