Add Continuous Integration

[Baklap4]

Do you want to request a feature or report a bug?

Feature

What did you expect to see?

Currently there's no Continuous integration. In other words this means we have to run the unit tests ourselves, check style coding etc, check if it builds. I bet we don't want that. We'd love to see this repetitive stuff to be automated as much as possible. Here comes CI around the corner.

Expectations

The CI should be able to do:

• Be triggered upon a push (commit or tags)
• Restore dependency packages
  • Run the command dotnet restore --packages SOME/LOCATION in the same folder as where the sln file is.
• Cache the dependencies so our buildtime will decrease
  • Run the previous command with the cached packages when the pipeline builds a second time.
• Build the project
  • Windows
  • Linux
  • OSx
• Run tests
  • Windows
  • Linux
  • OSx
• Once every night run a nightly build.

If the CI meets these expectations AND the push is a tag/release CD will pop up to release a new version. see #57

[Baklap4]

@loic-sharma i'd love to set this up with travis-ci, however i'd need access to the webhook area of this github page

[loic-sharma]

I was planning on onboarding to VSTS Pipelines once it's released. AFAIK there's no public information about VSTS Pipelines yet, so I won't say too much. Some of Microsoft's .NET projects like Kestrel are already using it.

What were you thinking of using for CI?

[Baklap4]

Hmm personally i'm not a big fan of VSTS, since it was so hard to configure (1 year ago) and let it do what it should be doing. Let be creating a docker image or such.. therefore I moved to gitlab which was way easier. Here on Github most of the people do use travis or jenkins to do what they want

[WernerMairl]

I have my own CI Build System here (Jenkins, Docker, implemented in pwsh on Linux)

I like the idea to define/implement a few basic entry points and scripts that can be used from multiple
CI-Systems.....

to avoid deep/hard dependencies into ONE CI-Build system, so we are open for

• VSTS (Pipeline or Classic)
• travis et. al
• custom/on premise systems

that may by a litle bit more of work, but it should bring back a lot of learnings in this area!

what you think about that ?

[loic-sharma]

Added Travis CI as part of a4ddace. Feel free to open more issues if you have more ideas! 😄

[loic-sharma]

Reopening this. The current set up doesn't run unit tests.

[loic-sharma]

Travis will now run the tests as part of the build. Closing this again. Apologies for the noise!

[kirkone]

Hi,

Azure DevOps Pipelines are available now and free to use for open source projects. I think it is worth to give it a try.
What do you think?

Greetings,
KirK

[loic-sharma]

@kirkone Yup, I'm working on this. See: https://sharml.visualstudio.com/BaGet 😄

[kirkone]

@loic-sharma if I can provide any help please let me know.
Maybe .yaml files are a good starting point.

[loic-sharma]

I’ve created an Azure Pipelines YAML file here: https://github.com/loic-sharma/BaGet/blob/master/.azure/pipelines/ci-official.yml

Please let me know if you have any suggestions. I’ll add GitHub release mechanisms in the future.