Windows builds are not pushed to openrct2.org after VS2017 remove #5010

Closed
Lastorder-DC opened this Issue Jan 7, 2017 · 0 comments

Projects

None yet

1 participant

@Lastorder-DC
Contributor
Lastorder-DC commented Jan 7, 2017 edited

This is caused by removed VS2017 Builds.
since there're only one image configured at build, appveyor did not include image name at job name, causing deploy script think that build is not coming from VS2015.

@Lastorder-DC Lastorder-DC added a commit to Lastorder-DC/OpenRCT2 that referenced this issue Jan 7, 2017
@Lastorder-DC Lastorder-DC Fix #5010 windows builds not pushed
windows builds not pushed to openrct2.org due to invalid condition
fab50b1
@Lastorder-DC Lastorder-DC added a commit to Lastorder-DC/OpenRCT2 that referenced this issue Jan 7, 2017
@Lastorder-DC Lastorder-DC Fix #5010 windows builds not pushed
windows builds not pushed to openrct2.org due to invalid condition
683e735
@Lastorder-DC Lastorder-DC added a commit to Lastorder-DC/OpenRCT2 that referenced this issue Jan 7, 2017
@Lastorder-DC Lastorder-DC Fix #5010 windows builds not pushed
windows builds not pushed to openrct2.org due to invalid condition
742ab6f
@Lastorder-DC Lastorder-DC added a commit to Lastorder-DC/OpenRCT2 that referenced this issue Jan 7, 2017
@Lastorder-DC Lastorder-DC Fix #5010 windows builds not pushed
windows builds not pushed to openrct2.org due to invalid condition
83a015d
@IntelOrca IntelOrca added a commit that closed this issue Jan 7, 2017
@Lastorder-DC @IntelOrca Lastorder-DC + IntelOrca Fix #5010 windows builds not pushed
windows builds not pushed to openrct2.org due to invalid condition
84d2f6c
@IntelOrca IntelOrca closed this in 84d2f6c Jan 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment