Skip to content

[CI] Remove codebuild configuration. #5536

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.

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

Merged
merged 1 commit into from
Feb 20, 2021

Conversation

NlightNFotis
Copy link
Contributor

@NlightNFotis NlightNFotis commented Oct 20, 2020

Since we have now implemented most jobs on github
actions, it makes sense to depend on that and remove
codebuild, as this has multiple benefits:

  1. It makes it easier for project contributors to
    see the result of the builds of their PRs (in
    codebuild, it was very complicated to access
    the build results, and as a matter of fact we
    had special instructions for accessing them).
  2. It removes the maintenance burden from us to maintain
    multiple CI systems, especially since there are not
    obvious benefits to doing so.
  3. We no longer need to have so many jobs needed for one
    PR, which used to create multiple problems, as it was
    the case that some jobs would always fail in some way
    (like fail to be initialised).
  • Each commit message has a non-empty body, explaining why the change was made.
  • Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • White-space or formatting changes outside the feature-related changed lines are in commits of their own.

Copy link
Collaborator

@martin-cs martin-cs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming that we have all of the same platform / configurations for building in the github CI as codebuild -- sure! I know this wasn't the case when moving from Travis to codebuild.

@martin-cs
Copy link
Collaborator

That said -- why is codebuild being run on this PR?

@NlightNFotis
Copy link
Contributor Author

@martin-cs It's not being run - it's being triggered because it's hooked into the repository's settings, but because of the config being removed, it's hanged.

I have asked @peterschrammel to review it, and if he thinks it's good, to review the required status from these checks, so they are no longer there.

This isn't new - same thing happened when we removed travis :)

Copy link
Member

@peterschrammel peterschrammel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which are the mandatory jobs now?

@thomasspriggs
Copy link
Contributor

The codebuild jobs include a Linux + clang compiler build, which as far as I can see hasn't been ported to git hub actions yet. I think there may be value in porting this over, before we abolish code build. A Linux + clang compiler job may be useful for isolating whether build failures on mac are due to using the Clang compiler or due to the standard library versions they use. In addition, the error messages from Clang can sometimes be easier to read than the ones from gcc.

@NlightNFotis
Copy link
Contributor Author

Okay, #5559 was now created to introduce the missing build to github actions, so we now all previous codebuild jobs should be ported to github actions.

Copy link
Collaborator

@tautschnig tautschnig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe I'm completely wrong here, but wouldn't we lose the Codecov integration? I'm not sure which of the two buildspec-linux-*-gcc-cov.yml is currently taking care of this, but they might still be needed?

Since we have now implemented most jobs on github
actions, it makes sense to depend on that and remove
codebuild, as this has multiple benefits:

1) It makes it easier for project contributors to
   see the result of the builds of their PRs (in
   codebuild, it was very complicated to access
   the build results, and as a matter of fact we
   had special instructions for accessing them).
2) It removes the maintenance burden from us to maintain
   multiple CI systems, especially since there are not
   obvious benefits to doing so.
3) We no longer need to have so many jobs needed for one
   PR, which used to create multiple problems, as it was
   the case that some jobs would always fail in some way
   (like fail to be initialised).
@codecov
Copy link

codecov bot commented Feb 17, 2021

Codecov Report

Merging #5536 (2d3a5b7) into develop (81ecf05) will increase coverage by 0.01%.
The diff coverage is 78.84%.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #5536      +/-   ##
===========================================
+ Coverage    72.84%   72.86%   +0.01%     
===========================================
  Files         1421     1421              
  Lines       154138   154171      +33     
===========================================
+ Hits        112289   112331      +42     
+ Misses       41849    41840       -9     
Impacted Files Coverage Δ
src/goto-programs/goto_convert_class.h 87.30% <ø> (ø)
src/solvers/flattening/boolbv_union.cpp 57.14% <0.00%> (ø)
src/solvers/flattening/boolbv_with.cpp 65.30% <0.00%> (ø)
src/solvers/flattening/boolbv.h 69.56% <50.00%> (ø)
src/solvers/flattening/bv_pointers.cpp 80.89% <73.94%> (ø)
src/goto-programs/builtin_functions.cpp 54.57% <94.11%> (+1.03%) ⬆️
src/ansi-c/c_typecheck_expr.cpp 74.42% <100.00%> (+0.40%) ⬆️
src/solvers/flattening/boolbv_byte_extract.cpp 70.00% <100.00%> (ø)
src/solvers/flattening/boolbv_byte_update.cpp 100.00% <100.00%> (ø)
src/solvers/flattening/boolbv_width.cpp 76.69% <100.00%> (ø)
... and 16 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eeb48a2...2d3a5b7. Read the comment docs.

@NlightNFotis
Copy link
Contributor Author

@tautschnig Hi Michael, can you take another look at this?

We have ported almost all of the jobs to GitHub Actions now (the ones missing are ones based on outdated configuration, like clang-3.8, and some windows setups like building under msbuild) and we have coverage and extra macOS jobs now.

Does this look more fit for purpose now?

@NlightNFotis NlightNFotis changed the title Remove codebuild configuration. [CI] Remove codebuild configuration. Feb 19, 2021
@tautschnig tautschnig merged commit 46de6f6 into diffblue:develop Feb 20, 2021
@NlightNFotis NlightNFotis deleted the remove_codebuild branch February 22, 2021 00:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants