Hi,
I found a quite interesting tool called Overcommit [1].
It provides an easy way for setting up Git commit hooks and provides
some basic checking plugins.
The nice feature of the Git commit hooks is that you can run some checks
automatically and early in the development. For example with the commit hooks you can
run Rubocop check automatically whenever a commit is created. And if the check fails
the commit is not created.
I can see "make Rubocop happy" commits quite often (happens to me as well),
with Overcommit you can easily avoid that.
I have tried several Overcommit checks:
- Rubocop - runs Rubocop at "commit"
- Rspec - runs the tests before "push"
- Branch blacklist - can forbid direct commits to configured branches,
e.g. "master" (forces using pull requests, avoids commits to master my mistake)
- Commit message spellcheck - warns when there is a possible typo
Check my blog post [2] for the details, esp. watch the recorded screencast where
I wanted to show some mistakes which it can catch.
The tool looks promising, I'll try using it for some time. If you want to try it
as well check the blog post for the installation steps.
Enjoy!
[1] https://github.com/brigade/overcommit
[2] http://blog.ladslezak.cz/2016/06/06/overcommit/
--
Ladislav Slezák
Appliance department / YaST Developer
Lihovarská 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak(a)suse.com
SUSE
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi all,
some time ago we discussed where and how we should share
"Tips&Tricks" for YaST users and developers.
IIRC there was no clear conclusion so I decided to start
a wiki [1] to collect all our tricks we know or use.
For now it's just a place for dumping your ideas, links, short
howtos, etc... When we collect enough data we can probably
split it to several categories or move it somewhere else.
We just need the data first.
I have added there some my tricks from my personal "knowledgebase"
file. If you have better tricks or find something wrong simply
change it, it's a wiki ;-)
Ladislav
[1] https://github.com/yast/yast.github.io/wiki/YaST-Tips-and-Tricks
--
Ladislav Slezák
YaST Developer
SUSE LINUX, s.r.o.
Corso IIa
Křižíkova 148/34
18600 Praha 8
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
Travis recently enabled a new auto cancellation feature.
If you commit a new change Travis can automatically cancel the old
builds in the queue. That means you should get the results
for the latest change faster.
See more details at the Travis blog [1].
To me it looks like a nice feature.
The only drawback is that if you really use the strict TDD approach
(write a failing test first then create a fix, like I did here [2])
then you would have to wait a bit between pushing the test and the fix.
At least until the first build starts.
But that is usually not the case is our workflow so it should not be
an issue and we could use this feature by default.
So any reason why NOT using the auto cancellation feature? Otherwise I'd
enable it globally for all Travis jobs...
Lada
[1] https://blog.travis-ci.com/2017-03-22-introducing-auto-cancellation
[2] https://github.com/yast/yast-yast2/pull/570
--
Ladislav Slezák
YaST Developer
SUSE LINUX, s.r.o.
Corso IIa
Křižíkova 148/34
18600 Praha 8
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi all,
Yesterday I published a short blog post about recording a screencast
(a desktop session) to create a video or an animated image.
So if you want to have nice animated images in READMES [1] or in pull requests [2]
then check this post [3].
Enjoy!
[1] https://github.com/lslezak/build-rake/blob/master/README.md
[2] https://github.com/yast/yast-registration/pull/240
[3] http://lslezak.blogspot.cz/2016/01/recording-screencast-in-linux.html
--
Ladislav Slezák
Appliance department / YaST Developer
Lihovarská 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak(a)suse.com
SUSE
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
With a little bit of delay, the latest YaST Team development report has
finally arrived. Enjoy it at
https://lizards.opensuse.org/?p=12416
Cheers.
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi all,
Travis runs Ubuntu 12.04 in some jobs but Canonical is ending
the official support on April 28th (i.e. this Friday).
Some notes:
- Travis builds will still use the 12.04 version even after
the EOL date.
- Upgrade to Ubuntu 14.04 LTS is planned at Q3 (probably at July)
(ugh? I'd expect upgrade to 16.04 LTS to avoid the same
situation soon...)
See more details at https://blog.travis-ci.com/2017-04-17-precise-EOL
How this will affect us?
- As we switched to Docker at Travis and run the builds
inside an openSUSE Tumbleweed container this should not affect
us at all in the "master" branch. Moreover it seems that for
the "master" branch Travis already uses the 14.04 version.
(I have checked few packages and all were running in 14.04.)
- However, the problem can be expected with the SLE-12-SP2 branch
and older as these still run in 12.04.
That means we will probably need to switch to Docker also in
the older branches, at least in SP2 + CASP, SP1 would be nice
as well I guess.
(An alternative approach could be building the packages in OBS
for the 14.04 version but that might be tricky so I'd prefer
the Docker solution.)
I have created a Trello card to track it: https://trello.com/c/V0OaC4DT
--
Ladislav Slezák
YaST Developer
SUSE LINUX, s.r.o.
Corso IIa
Křižíkova 148/34
18600 Praha 8
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
JFYI: I have publilshed a short blog post about using the `ts` tool
for time-stamping program output.
I used it for profiling an rspec test but it can be helpful in many other
situations.
https://blog.ladslezak.cz/2017/04/24/time-stamping-stdout-and-profiling/
--
Ladislav Slezák
YaST Developer
SUSE LINUX, s.r.o.
Corso IIa
Křižíkova 148/34
18600 Praha 8
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org