Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deep review and rework of build infrastructure #325

Closed
2 tasks done
simonbasle opened this issue Dec 22, 2016 · 2 comments
Closed
2 tasks done

Deep review and rework of build infrastructure #325

simonbasle opened this issue Dec 22, 2016 · 2 comments
Labels
type/chores A task not related to code (build, formatting, process, ...)

Comments

@simonbasle
Copy link
Member

simonbasle commented Dec 22, 2016 •
edited
Loading

  • Make sure which tests (spock, testng/tck, junit "classic" vs "loops") run at which step (PR, snapshot, milestone...)
  • Review the gradle test tasks and how they are rewritten in the build.gradle
  • Review all .gradle files. Notably setup.gradle doesn't add the Implementation-Version where it should (see Manifest is missing "Implementation-Version" #316)
  • Maybe add a nightly bamboo build that will run all tests
@simonbasle simonbasle added the type/enhancement A general enhancement label Dec 22, 2016
@simonbasle simonbasle added this to the 3.1.0.RELEASE milestone Dec 22, 2016
@simonbasle simonbasle changed the title Deep review and rework of build Deep review and rework of build infrastructure Dec 22, 2016
@smaldini
Copy link
Contributor

smaldini commented Jun 1, 2017 •
edited
Loading

Probably worth tracking/reference any discussed investigation on build pipeline along this this @rajinisivaram

@smaldini smaldini modified the milestones: 3.1.0.RELEASE, 3.2.0.RELEASE Jun 12, 2017
@simonbasle simonbasle added type/chores A task not related to code (build, formatting, process, ...) and removed type/enhancement A general enhancement labels Jun 30, 2017
simonbasle added a commit that referenced this issue Jan 4, 2018
@simonbasle
see #325 [build] Improve build configuration for tests (#1007)
b9e3aa9 
 - better common configuration
 - clearer sequencing of events
 - additional tests are more clearly segregated
   and will still run when explicitly called
 - testNG is only exluded from check when
   building on Travis
 - loops is always excluded from check when
   building a SNAPSHOT
 - Travis fast_finish: do not wait for JDK9
   job to finish before setting the build status
@simonbasle simonbasle modified the milestones: 3.2.0.RELEASE, [backlog] Mar 2, 2018
@smaldini smaldini removed this from the Backburner milestone Jun 11, 2019
@smaldini
Copy link
Contributor

Need to precise this issue for any CI change on a different detailed issue if necessary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/chores A task not related to code (build, formatting, process, ...)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@smaldini @simonbasle