Skip to content

Conversation

@jamesxu123
Copy link
Member

@jamesxu123 jamesxu123 commented Jun 19, 2021

Tickets:

List of changes:

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

  • Move CI/CD to GitHub Actions due to deprecation of travis-ci.org

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • New release
  • This change requires a documentation update

How has this been tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Test Configuration:

Firmware version:
Hardware:
Toolchain:
SDK:

Questions for code reviewers?

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • Listed change(s) in the Changelog
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have made corresponding changes to the documentation
  • Any dependent changes have been merged and published in downstream modules

logan-r and others added 6 commits January 22, 2021 21:07
* feat: Hacker location fields (#687)

* feat: add additional optional fields for hacker location

* feat: update documentation to include hacker location

* feat: update emails and bump version

Co-authored-by: Tony <36376980+Tony9984@users.noreply.github.com>
@jamesxu123 jamesxu123 temporarily deployed to testing June 21, 2021 01:15 Inactive
@jamesxu123 jamesxu123 changed the title Create node.js.yml fix: move ci/cd to github actions Jun 21, 2021
@jamesxu123 jamesxu123 temporarily deployed to testing June 21, 2021 01:18 Inactive
@jamesxu123 jamesxu123 self-assigned this Jun 21, 2021
push:
branches: [ dev ]
pull_request:
branches: [ dev ]
Copy link
Member

Choose a reason for hiding this comment

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

How about master branch? In case someone pushes to that branch in a rush right before the hackathon.

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks for that. I forgot about master!

@jamesxu123 jamesxu123 temporarily deployed to testing June 21, 2021 01:58 Inactive
Copy link
Member

@krubenok krubenok left a comment

Choose a reason for hiding this comment

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

Overall, looks fine, but I think it'd be good to either merge #691 first or merge that branch into this so that we can have a full view of the impact on CI/CD before calling it good.

Also: travis.yml should be deleted as part of this PR.

Edit: this would also close #660

Comment on lines 2 to 14
<component name="GithubSharedProjectSettings">
<option name="branchProtectionPatterns">
<list>
<option value="master" />
<option value="dev" />
</list>
</option>
</component>
<component name="VcsDirectoryMappings">
<mapping directory="$PROJECT_DIR$" vcs="Git" />
</component>
</project>
</project>
Copy link
Member

Choose a reason for hiding this comment

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

Does anyone still use Jetbrains IDEs? Can this whole .idea folder be deleted?

Copy link
Member Author

Choose a reason for hiding this comment

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

I use PhpStorm, let's keep it for now.

@jamesxu123
Copy link
Member Author

Overall, looks fine, but I think it'd be good to either merge #691 first or merge that branch into this so that we can have a full view of the impact on CI/CD before calling it good.

Also: travis.yml should be deleted as part of this PR.

Edit: this would also close #660

#691 is still in progress and it's estimated to take quite a long time because a lot of manual work is involved. Since Travis is deprecated, I believe it's best to get something functional in place so our other PRs won't be blocked. Good catch on the deletion of travis.yml though thanks!

@jamesxu123 jamesxu123 temporarily deployed to testing June 21, 2021 02:40 Inactive
@jamesxu123 jamesxu123 temporarily deployed to testing June 21, 2021 02:41 Inactive
@jamesxu123 jamesxu123 temporarily deployed to testing June 21, 2021 02:42 Inactive
@jamesxu123 jamesxu123 temporarily deployed to testing June 21, 2021 02:46 Inactive
Copy link
Member

@krubenok krubenok left a comment

Choose a reason for hiding this comment

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

🚢 it!

Maybe time to investigate re-enabling dependabot now to start bailing out of dependency hell

@jamesxu123 jamesxu123 merged commit e6f721e into dev Jun 21, 2021
@jamesxu123 jamesxu123 deleted the feature/hac-32-investigate-new-cicd-system-for branch June 21, 2021 03:38
@jamesxu123 jamesxu123 mentioned this pull request Jun 21, 2021
logan-r added a commit that referenced this pull request Nov 29, 2021
* release: version 3.1.2 (#689)

* feat: Hacker location fields (#687)

* feat: add additional optional fields for hacker location

* feat: update documentation to include hacker location

* feat: update emails and bump version

Co-authored-by: Tony <36376980+Tony9984@users.noreply.github.com>

* merge and resolve conflicts

* Create node.js.yml

* Update node.js.yml

* Update node.js.yml

* Update app.js

* Update node.js.yml

* Update node.js.yml

* Update node.js.yml

* Update node.js.yml

* Update node.js.yml

* Update node.js.yml

* Update node.js.yml

* Update node.js.yml

* Update node.js.yml

* Update node.js.yml

* Update node.js.yml

* Update node.js.yml

* Update node.js.yml

* Update package.json

* Update account.test.js

* Update account.test.js

* add elastic apm to see where tests are going wrong

* move apm to app.js so it gets picked up by test

* add apm env to gh workflow

* add missing envs

* remove debugging tools

* remove elastic apm

* run ci/cd on master as well

* Update .nvmrc

* Update package.json

* Delete .travis.yml

* Update package.json

Co-authored-by: Logan Ralston <logan.ralston@mail.mcgill.ca>
Co-authored-by: Tony <36376980+Tony9984@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants