A VSTS build task that helps you build and release Docker containers.
Shell JavaScript
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.vscode
lambda3docker
screenshots
.gitattributes
.gitignore
LICENSE.txt
README.md
overview.md
package.json
vss-extension.json

README.md

Docker build Tasks

A VSTS build task that helps you build and release Docker containers.

This is a community project, free and open source. Everyone is invited to contribute, fork, share and use the code. No money shall be charged by this software, nor it will be. Ever.

Installing

You should go to the Visual Studio Marketplace and install from there. Here you will find this extension.

You can also checkout the overview page which contains the info displayed on the Marketplace.

Contributing

Questions, comments, bug reports, and pull requests are all welcome. Bug reports that include steps-to-reproduce (including code) are preferred. Even better, make them in the form of pull requests. Before you start to work on an existing issue, check if it is not assigned to anyone yet, and if it is, talk to that person.

Issues

Pull request

When you are done, pull the changes from the master branch.

If you know git well, you can rebase your changes instead of merging them. If not, it is ok to merge them. When your changes are up to date with the master branch then you should push them to your Github repo and then you will be able to issue a pull request and mention the issue you were working on. Make your PR message clear. If when you are creating the pull request on Github it mentions that the PR cannot be merged because there are conflicts it means you forgot to integrate the master branch. Correct that push the changes to your personal repo. This will automatically update the PR. The project maintainers should not have to resolve merge conflicts, you should.

Rules for contribution

  • Must mention an existing issue on Github
  • Don't reformat any code but the one you produced
  • Follow the coding standards already in place within the project

If you work on something that you have not yet discussed with the maintainers there is a chance the code might be denied. They are easily reachable through Twitter or on Github. Before you code discuss it with it them.

Maintainers/Core team

Contributors can be found at the contributors page on Github.

Contact

Twitter is the best way.

License

This software is open source, licensed under the Apache License, Version 2.0. See LICENSE.txt for details. Check out the terms of the license before you contribute, fork, copy or do anything with the code. If you decide to contribute you agree to grant copyright of all your contribution to this project, and agree to mention clearly if do not agree to these terms. Your work will be licensed with the project at Apache V2, along the rest of the code.