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

Set up appveyor.yaml and build #21

Closed
ferventcoder opened this issue Jan 18, 2015 · 8 comments
Closed

Set up appveyor.yaml and build #21

ferventcoder opened this issue Jan 18, 2015 · 8 comments
Assignees
@ferventcoder
Labels
BuildAutomation

Comments

@ferventcoder
Copy link
Member

No description provided.

@ferventcoder ferventcoder self-assigned this Jan 18, 2015
@gep13
Copy link
Member

gep13 commented Jan 18, 2015

If you wanted to add me to the team in AppVeyor, I would happily take a look at this.

@ferventcoder
Copy link
Member Author

Yes, just be sure to Self assign the task and move it to working.

On Sunday, January 18, 2015, Gary Ewan Park notifications@github.com
wrote:

If you wanted to add me to the team in AppVeyor, I would happily take a
look at this.

—
Reply to this email directly or view it on GitHub
#21 (comment).

Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

@ferventcoder ferventcoder removed their assignment Jan 18, 2015
@ferventcoder
Copy link
Member Author

Actually I might grab this so it falls under my account.

ferventcoder added a commit to ferventcoder/choco that referenced this issue Jan 18, 2015
@ferventcoder
(chocolateyGH-21) Add initial AppVeyor configuration
16c0a0a
ferventcoder added a commit to ferventcoder/choco that referenced this issue Jan 18, 2015
@ferventcoder
(chocolateyGH-21) AppVeyor tweaks
6939483 
- Add an init to set git user email and name
- Set certain test categories to be ignored
- Remove xml artifacts that have html equivalents
- Add buildinfo.xml
- Add detailed build log file
ferventcoder added a commit that referenced this issue Jan 18, 2015
@ferventcoder
(GH-21) AppVeyor - set git config options globally
c6cab2b 
The init script will error unable to lock the local config file so set
the options globally.
ferventcoder added a commit that referenced this issue Jan 18, 2015
@ferventcoder
(GH-21) AppVeyor Build status only master branch
2d053e1 
Only show the build status for the master branch. Otherwise confusion
could ensue if there is a PR that causes the build to fail.
ferventcoder added a commit that referenced this issue Jan 18, 2015
@ferventcoder
(GH-21) set clone depth to 5
0337e02
ferventcoder added a commit that referenced this issue Jan 18, 2015
@ferventcoder
(GH-21) gather nupkgs as artifacts
e26dcf8
@ferventcoder ferventcoder self-assigned this Jan 18, 2015
@ferventcoder
Copy link
Member Author

Trying to determine a good notification list - think we'll want to set up a mailing list for build status. That way we don't diverge emails and people can self-subscribe.

ferventcoder added a commit that referenced this issue Jan 18, 2015
@ferventcoder
(GH-21)(doc) Add build status email group
ad31608 
This will allow different build / integration systems to send email to
a group that folks can self-subscribe to.
@ferventcoder
Copy link
Member Author

Actually added that. That way any build/integration tool can email build status changes to a mailing list.

ferventcoder added a commit that referenced this issue Jan 18, 2015
@ferventcoder
(GH-21) change notification subject
ba06d84 
Identify the system sending the message, note that the message is a
build notification (could include a pass/fail due to email on status
changes).
@ferventcoder
Copy link
Member Author

This is probably good enough now to close this issue. Any followup AppVeyor items should get a new ticket.

ferventcoder added a commit that referenced this issue Jan 18, 2015
@ferventcoder
(GH-21) appveyor artifacts do not allow wildcards
31f2965 
Follow up with a request to allow for this.
ferventcoder added a commit that referenced this issue Jan 18, 2015
@ferventcoder
(GH-21) fix nupkg inclusion
cb912d1 
So apparently wildcards are supported, the path for grabbing the nuget
packages needed to be adjusted to be relative.
ferventcoder added a commit that referenced this issue Jan 18, 2015
@ferventcoder
(GH-21) Don't publish Nuget pkgs for PRs
2569887
@gep13
Copy link
Member

gep13 commented Jan 18, 2015

Actually I might grab this so it falls under my account.

Yip, that is fine, what I was getting at was assigning a GitHub Team to the project that you set up in AppVeyor:

image

image

That way, you still own the Project, but other team members can edit stuff if required. This won't be as much of a big deal since we are driving everything through the appveyor.yml file, but still worth doing, IMO.

gep13 added a commit to gep13/choco that referenced this issue Jan 18, 2015
@gep13
Merge remote-tracking branch 'upstream/master'
afaf484 
* upstream/master:
  (chocolateyGH-21) Don't publish Nuget pkgs for PRs
  (chocolateyGH-21) fix nupkg inclusion
  (chocolateyGH-21) appveyor artifacts do not allow wildcards
  (doc) Submitting issues enhancements
  (chocolateyGH-21) change notification subject
  (chocolateyGH-21)(doc) Add build status email group
  (chocolateyGH-21) gather nupkgs as artifacts
  (chocolateyGH-21) set clone depth to 5
  (chocolateyGH-21) AppVeyor Build status only master branch
  (doc) readme - add links / fixup header
  (doc) Add badges
  (chocolateyGH-21) AppVeyor - set git config options globally
  (chocolateyGH-21) AppVeyor tweaks
  (chocolateyGH-21) Add initial AppVeyor configuration
  (log) list command escape curly braces
  (chocolateyGH-7) do not fail when deleting .old files
  (convention) methods/properties/events to inspect
  (doc) Help menu enhancements
@ferventcoder
Copy link
Member Author

I would love that.

On Sunday, January 18, 2015, Gary Ewan Park notifications@github.com
wrote:

Actually I might grab this so it falls under my account.

Yip, that is fine, what I was getting at was assigning a GitHub Team to
the project that you set up in AppVeyor:

[image: image]
https://cloud.githubusercontent.com/assets/1271146/5793811/d6b62592-9f49-11e4-8713-cd06b8992824.png

[image: image]
https://cloud.githubusercontent.com/assets/1271146/5793813/e4abfcda-9f49-11e4-844b-1d155c79947b.png

That way, you still own the Project, but other team members can edit stuff
if required. This won't be as much of a big deal since we are driving
everything through the appveyor.yml file, but still worth doing, IMO.

—
Reply to this email directly or view it on GitHub
#21 (comment).

Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ferventcoder ferventcoder

Labels
BuildAutomation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ferventcoder @gep13