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.

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

Update issues links and add travis config #3

Merged
merged 3 commits into from Jan 29, 2017

Conversation

Projects
None yet
2 participants
@lancew
Contributor

lancew commented Jan 27, 2017

Hi,
as part of CPAN-PRC I have updated the issue links to GItHub issues from RT.

I also added a travis config for automated testing. :-)

Lance

@karpet karpet self-assigned this Jan 28, 2017

@karpet

This comment has been minimized.

Show comment
Hide comment
@karpet

karpet Jan 28, 2017

Owner

Thanks for this effort.

I prefer to keep all bug reports in the CPAN RT. That keeps all my Perl stuff in the same place and allows for depedency tracking. Has there been some community conversation about moving away from RT about which I'm not aware?

I have not made any CI effort for these small libraries in Travis or other CI tools, since cpantesters exists. Is there a similar conversation about that?

Owner

karpet commented Jan 28, 2017

Thanks for this effort.

I prefer to keep all bug reports in the CPAN RT. That keeps all my Perl stuff in the same place and allows for depedency tracking. Has there been some community conversation about moving away from RT about which I'm not aware?

I have not made any CI effort for these small libraries in Travis or other CI tools, since cpantesters exists. Is there a similar conversation about that?

@lancew

This comment has been minimized.

Show comment
Hide comment
@lancew

lancew Jan 29, 2017

Contributor

Hi,

TravisCI seems to be gaining some real support as it has nice integrations with GitHub will run all the tests on all commits and pull requests. So if someone like me comes along with a pull request; it runs the tests so that any breakages are identified prior to it being accepted. For example if you take a look at lancew/Perl-Critic-Policy-Perlsecret#9 you can see where TravisCI has ticks and crosses showing when tests are passing or failing)

All before you do your release and it hitting cpantesters.

As for RT vs GitHub, mainly assumption on my part based on finding outstanding issues on GitHub and not on RT. :-)

Lance

Contributor

lancew commented Jan 29, 2017

Hi,

TravisCI seems to be gaining some real support as it has nice integrations with GitHub will run all the tests on all commits and pull requests. So if someone like me comes along with a pull request; it runs the tests so that any breakages are identified prior to it being accepted. For example if you take a look at lancew/Perl-Critic-Policy-Perlsecret#9 you can see where TravisCI has ticks and crosses showing when tests are passing or failing)

All before you do your release and it hitting cpantesters.

As for RT vs GitHub, mainly assumption on my part based on finding outstanding issues on GitHub and not on RT. :-)

Lance

@karpet karpet merged commit 64e7bb4 into karpet:master Jan 29, 2017

@karpet

This comment has been minimized.

Show comment
Hide comment
@karpet

karpet Jan 29, 2017

Owner

Fair enough. Thanks.

Owner

karpet commented Jan 29, 2017

Fair enough. Thanks.

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